https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66448
--- Comment #12 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Iain Sandoe from comment #11) > (In reply to Aldy Hernandez from comment #10) > > It's not supposed to. It's for issue three as stated. > > The test suite is running - was going to wait to report > until that's done … NOTE: I have bootstrapped and tested c,c++,objc,objc++,fortran,ada,lto - but NOT Java. So .. things are *very* much improved, thanks! (at least no reports during bootstrap), but there's still quite a bit of fallout in the testsuite (many more failing tests than listed below, these are just examples): FAIL: gcc.c-torture/execute/20020412-1.c -O3 -g (test for excess errors) FAIL: gcc.c-torture/execute/20040308-1.c -O3 -g (test for excess errors) FAIL: gcc.c-torture/execute/20070919-1.c -O3 -g (test for excess errors) FAIL: gcc.dg/torture/pr8081.c -O3 -g (test for excess errors) <etc> (usually several) instances of: warning: invalid DWARF generated by the compiler: DIE 0x0000018b has multiple AT_decl_file attributes in '/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccSyKR0x.o'. warning: invalid DWARF generated by the compiler: DIE 0x0000015d has multiple AT_decl_line attributes in '/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//cccckVUY.o'. FAIL: c-c++-common/cilk-plus/CK/cilk-for-2.c -g (test for excess errors) FAIL: c-c++-common/cilk-plus/CK/cilk-fors.c -g (test for excess errors) FAIL: c-c++-common/cilk-plus/CK/cilk_for_grain.c -g (test for excess errors) FAIL: c-c++-common/cilk-plus/CK/cilk_for_ptr_iter.c -g (test for excess errors) FAIL: c-c++-common/cilk-plus/CK/nested_cilk_for.c -g (test for excess errors) <etc> also plugin tests. (many) instances of: warning: invalid DWARF generated by the compiler: DIE 0x00000176 has multiple AT_artificial attributes in '/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccNJ6qak.o'. === looks like c++ only has fails of the form: has multiple AT_artificial attributes ===== no errors of this kind recorded in acats ===== gnat has all three forms ===== fortran seems to have only: AT_artificial attributes ====== target lib tests seem dominated by has multiple AT_artificial attributes (I didn't see any other cases in a quick grep)
