This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug regression/53203] New: [4.8 Regression]: gcc.dg/setjmp-1.c
- From: "hp at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 02 May 2012 21:42:29 +0000
- Subject: [Bug regression/53203] New: [4.8 Regression]: gcc.dg/setjmp-1.c
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53203
Bug #: 53203
Summary: [4.8 Regression]: gcc.dg/setjmp-1.c
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: regression
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hp@gcc.gnu.org
CC: bernds@gcc.gnu.org
Host: x86_64-unknown-linux-gnu
Target: cris-axis-elf
Created attachment 27292
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27292
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).