------- Comment #4 from joel at gcc dot gnu dot org 2009-03-17 17:32 ------- Going back through the old run logs. Is this how it shows up?
FAIL: gcc.c-torture/execute/built-in-setjmp.c execution, -O0 FAIL: gcc.c-torture/execute/built-in-setjmp.c execution, -O1 FAIL: gcc.c-torture/execute/built-in-setjmp.c execution, -O2 FAIL: gcc.c-torture/execute/built-in-setjmp.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/built-in-setjmp.c execution, -O3 -fomit-frame-pointer -funroll-loops FAIL: gcc.c-torture/execute/built-in-setjmp.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions FAIL: gcc.c-torture/execute/built-in-setjmp.c execution, -O3 -g FAIL: gcc.c-torture/execute/built-in-setjmp.c execution, -Os So far I see those in logs back to May 2008 (revision 135528): http://gcc.gnu.org/ml/gcc-testresults/2008-05/msg01876.html And apparently it failed in 4.3.0: http://gcc.gnu.org/ml/gcc-testresults/2008-05/msg00535.html And 4.2.3 http://gcc.gnu.org/ml/gcc-testresults/2008-04/msg00645.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35180
