spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir64/gcc/testsuite/g++2/../../xg++ - B/home/dave/gnu/gcc/objdir64/gcc/testsuite/g++2/../../ /home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/pch/line-map-3.C -fdiagnostics-plain-output -nostdinc++ -I/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/hppa64-hp-hpux11.11 -I/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include -I/home/dave/gnu/gcc/gcc/libstdc++-v3/libsupc++ -I/home/dave/gnu/gcc/gcc/libstdc++-v3/include/backward -I/home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/util -fmessage-length=0 -g -I. -Dwith_PCH -Werror=unused-macros -S -o line-map-3.s /home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/pch/line-map-3.C:3:9: error: macro "UNUSED_MACRO" is not used [-Werror=unused-macros] /home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/pch/line-map-3.C:3:9: error: macro "with_PCH" is not used [-Werror=unused-macros] cc1plus: some warnings being treated as errors compiler exited with status 1 XFAIL: g++.dg/pch/line-map-3.C -g -I. -Dwith_PCH (test for errors, line 1) XPASS: g++.dg/pch/line-map-3.C -g -I. -Dwith_PCH (test for bogus messages, line 2) XPASS: g++.dg/pch/line-map-3.C -g -I. -Dwith_PCH at line 17 (test for bogus messages, line 2) PASS: g++.dg/pch/line-map-3.C -g -I. -Dwith_PCH dg-regexp 23 was found: "[^[:space:]]*: some warnings being treated as errors" FAIL: g++.dg/pch/line-map-3.C -g -I. -Dwith_PCH (test for excess errors) Excess errors: /home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/pch/line-map-3.C:3:9: error: macro "UNUSED_MACRO" is not used [-Werror=unused-macros] /home/dave/gnu/gcc/gcc/gcc/testsuite/g++.dg/pch/line-map-3.C:3:9: error: macro "with_PCH" is not used [-Werror=unused-macros] Commit bad991a1c59 was okay. Similar fails: FAIL: g++.dg/pch/line-map-3.C -O2 -g -I. -Dwith_PCH (test for excess errors) FAIL: g++.dg/pch/line-map-3.C -O2 -I. -Dwith_PCH (test for excess errors)
Thanks, yes the test is problematic because the warnings it looks for are platform dependent. There is a patch to address it here: https://gcc.gnu.org/pipermail/gcc-patches/2024-January/644487.html. It's being tracked at the original PR, so marking as a dupe of that one. *** This bug has been marked as a duplicate of bug 105608 ***