Re: using `volatile' to silence gcc warnings

[Sam S. <sd...@gn...>]

> * Bruno Haible <oe...@py...> [2011-07-05 23:27:04 +0200]:
>
> Here the warning is pointless because the dangerous situation with setjmp()
> is that when it returns a nonzero value, the register-allocated local
> variables may have been clobbered (an effect typically only seen on SPARC
> CPUs, but I'm glad gcc warns about it on all platforms). Here the only
> setjmp() call is in the
>    finish_entry_frame(ITAGBODY,returner,, goto go_entry; );
> line, and when setjmp() has returned a nonzero value, the statement
>    body = value1;
> is executed.

ok, so this warning is a gcc bug.
Jerry, could you please file a gcc bug report?
thanks!

-- 
Sam Steingold (http://sds.podval.org/) on CentOS release 5.6 (Final) X 11.0.60900031
http://honestreporting.com http://www.PetitionOnline.com/tap12009/
http://ffii.org http://palestinefacts.org http://pmw.org.il http://memri.org
Never succeed from the first try - if you do, nobody will think it was hard.