https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54561
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54561
--- Comment #4 from Mikael Pettersson mikpelinux at gmail dot com ---
(In reply to Matthieu Patou from comment #3)
volatile proto_tree *tmptree = NULL;
Try
proto_tree * volatile tmptree = NULL;
It's the variable itself that needs to be
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54561
Matthieu Patou mat at matws dot net changed:
What|Removed |Added
CC||mat at matws dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54561
--- Comment #1 from Andrew Pinski pinskia at gcc dot gnu.org 2012-09-12
21:02:37 UTC ---
Both info_ptr and fp are alive across the setjmp. GCC does not do fancy
detection of alive on one of branches of the result of setjmp. It just warns
if it
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54561
--- Comment #2 from eggert at gnu dot org 2012-09-12 23:39:16 UTC ---
GCC ... warns if it is alive across on either branch on setjmp.
OK, thanks, that's the bug then. GCC should warn only about the
longjmp branch, not about the non-lonjmp
