http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
eggert at gnu dot org changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|FIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
--- Comment #7 from eggert at gnu dot org 2012-06-01 21:19:16 UTC ---
Created attachment 27546
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27546
alternate test case, for x86, showing "({anonymous}) might be clobbered"
By compiling on x86 (
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
eggert at gnu dot org changed:
What|Removed |Added
Version|4.6.0 |4.7.0
--- Comment #6 from eggert a
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
--- Comment #5 from eggert at gnu dot org 2011-05-12 19:52:20 UTC ---
A register may be live (after inlining), but the local variable XXXevent is not
live across the setjmp call, so surely the warning is wrong even if the
generated code is correct.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
--- Comment #3 from Andreas Schwab 2011-05-12 11:00:16
UTC ---
That function doesn't actually call setjmp.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
--- Comment #2 from Richard Guenther 2011-05-12
09:11:45 UTC ---
Well, XXXevent is scalarized by SRA (-fno-tree-sra gets rid of the error) and
I suppose nothing prevents that register to be propagated to other indirect
uses. So it might be indee
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
--- Comment #1 from eggert at gnu dot org 2011-05-11 19:35:32 UTC ---
Created attachment 24227
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24227
gzip-compressed u.i program, illustrating incorrect diagnostic
10 matches
Mail list logo
