[Bug middle-end/31707] Spurious "'<variable>' may be used uninitialized in this function" warnings when using __builtin_setjmp and loops and extern function call

[hackbunny at reactos dot com]

------- Comment #7 from hackbunny at reactos dot com  2008-05-26 14:17 -------
(In reply to comment #6)
> but of which are really only used for Ada eh usage really.

and C++ for SJLJ exceptions. No? The library I use it in is a custom exception
handling library, that integrates with the Windows exception handling ABI in a
way that GCC can't (yet). As unfortunate artifacts of user-visible syntax, the
code is full of hacks - local variables I expect to be const-folded or
otherwise inlined, bogus loops, bogus conditionals. GCC always had difficulty
with it, producing code like "set register to 1; if register equals 1 then...",
but GCC 4.2 is the first release that actually hurts our build with spurious
warnings

>From tree dumps and disassemblies I can see a significant change in how
__builtin_setjmp is emitted between 4.1 and 4.2, and that's all I know about
it. I have no real interest in GCC internals

Can this issue at least be confirmed as NEW, though? or I'm afraid it will
never even get a chance to be looked at by someone else


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31707