> > PASS-FAIL: gcc.c-torture/execute/980707-1.c execution, -O3 > > -fomit-frame-pointer > > Can you pin-point the patch that caused this and investigate what is > going wrong?
Looks like a schroedinbug. The .s file from before ("pass") is obviously wrong, but the right value *happens* to be in the right register at the right time to cause the test to pass. The non-related patch perturbed the compiler just enough to alter the way the program was optimized (strange but true), which changed the "just happens" into a "doesn't".