FAIL: gcc.target/i386/ssefn-1.c scan-assembler-not movsd FAIL: gcc.target/i386/ssefn-1.c scan-assembler-not mulsd FAIL: gcc.dg/tree-ssa/gen-vect-11b.c scan-tree-dump-times vectorized 0 loops 1 FAIL: gcc.dg/tree-ssa/gen-vect-11c.c scan-tree-dump-times vectorized 0 loops 1 FAIL: gcc.dg/builtin-apply4.c execution test FAIL: gcc.dg/compat/vector-2 c_compat_x_tst.o-c_compat_y_tst.o execute if you need preprocessed sources - let me know.
So, far gcc-4.2,2 is fine with GCC suite test results like: # of expected passes 42222 # of unexpected failures 10 # of expected failures 116 # of unresolved testcases 1 # of untested testcases 28 # of unsupported tests 293
These failures, and the ones in PR33365 and PR33366, don't show up in any of the archived test summaries for 4.2.2 on i686-unknown-linux-gnu linked from http://gcc.gnu.org/gcc-4.2/buildstat.html. Could they be due to hardware problems on the test machine? It's also possible that the configuration was different, such as defaulting to pentium4 instead of i686. Test failures get more interest when they still occur in trunk or are shown to be regressions for an identical configuration, meaning the tests passed for an earlier version. If either of those are true, please provide additional information.
gcc 4.2.x is no longer supported.
.