Created attachment 27292 [details]
repeat with "cc1 -fpreprocessed setjmp-1.i -quiet -O -Wclobbered -Wextra -Wall -fno-diagnostics-show-caret"
This test previously passed, now it fails.
A patch in the revision range (last_known_working:first_known_failing) 187015:187022
exposed or caused this regression. Since then it fails as follows:
Running /tmp/hpautotest-gcc0/gcc/gcc/testsuite/gcc.dg/dg.exp ...
FAIL: gcc.dg/setjmp-1.c spurious clobbered warning (test for bogus messages, line 16)
Lines in gcc.log:
/tmp/hpautotest-gcc0/gcc/gcc/testsuite/gcc.dg/setjmp-1.c: In function 'compare_float':
/tmp/hpautotest-gcc0/gcc/gcc/testsuite/gcc.dg/setjmp-1.c:16:23: warning: argument 'a' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]
/tmp/hpautotest-gcc0/gcc/gcc/testsuite/gcc.dg/setjmp-1.c:16:33: warning: argument 'b' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]
Author of suspect patch in revision range CC:ed.
Preprocessed setjmp-1.i attached; the regression might be related to the actual target-specific setjmp implementation (though simple and non-surprising, non-inline).
This seems connected to PR53176 but the reasons aren't obvious. Now that PR53176 is fixed, this went (back) into hiding; the test now passes. I think there's a deeper issue so I'm just suspending this PR, not resolving as fixed.
GCC 4.8.0 is being released, adjusting target milestone.
GCC 4.8.1 has been released.
GCC 4.8.2 has been released.
GCC 4.8.3 is being released, adjusting target milestone.
GCC 4.8.4 has been released.
The gcc-4_8-branch is being closed, re-targeting regressions to 4.9.3.
GCC 4.9.3 has been released.
GCC 4.9 branch is being closed
Cannot reproduce. Can we close this?
I guess it's of no use keeping this PR open if it
- gets on people's radars just for being open
- is hidden since long (with no known reproducer)
- has been out of the reporter's mind for at least four years
- triggers the reporter to sheepishly list at least three reasons to close it
Thus closed. I guess WORKSFORME fits best.