Bernardo Innocenti wrote: > I'm currently bootstrapping 4.2 with "--with-arch=geode" > and will run the testsuite shortly.
It took a little longer than I expected because I was seeing a few new regressions: FAIL: gcc.c-torture/execute/20050316-2.c execution, -O0 FAIL: gcc.c-torture/execute/20050316-2.c execution, -O1 FAIL: gcc.c-torture/execute/20050316-2.c execution, -O2 FAIL: gcc.c-torture/execute/20050604-1.c execution, -O0 FAIL: gcc.c-torture/execute/20050604-1.c execution, -O1 FAIL: gcc.c-torture/execute/20050604-1.c execution, -O2 FAIL: gcc.c-torture/execute/20050604-1.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/20050604-1.c execution, -O3 -fomit-frame-pointer -funroll-loops FAIL: gcc.c-torture/execute/20050604-1.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions FAIL: gcc.c-torture/execute/20050604-1.c execution, -O3 -g FAIL: gcc.c-torture/execute/20050604-1.c execution, -Os FAIL: gcc.dg/compat/vector-2 c_compat_x_tst.o-c_compat_y_tst.o execute FAIL: gcc.dg/builtin-apply4.c execution test But then it turned out that using --with-arch=athlon produces exactly the same regressions, while --with-arch=i586 is fine. I analyzed only the first failing test. It seems we fail with all MMX enabled processors. But maybe the test has invalid expectations, I'm not sure what it is trying to do. WORKS: gcc -O0 -march=i686 gcc.c-torture/execute/20050316-2.c && ./a.out FAILS: gcc -O0 -march=athlon gcc.c-torture/execute/20050316-2.c && ./a,out This is with 4.2-branch, but it also happens with FC6's gcc-4.1.1. -- // Bernardo Innocenti \X/ http://www.codewiz.org/
