This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/31707] Spurious "'<variable>' may be used uninitialized in this function" warnings when using __builtin_setjmp and loops and extern function call
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Apr 2007 22:59:25 -0000
- Subject: [Bug middle-end/31707] Spurious "'<variable>' may be used uninitialized in this function" warnings when using __builtin_setjmp and loops and extern function call
- References: <bug-31707-14467@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from pinskia at gcc dot gnu dot org 2007-04-25 23:59 -------
The problem is that the CFG does not know that the first time through the loop
when calling bar, you cannot get to the setjmp. This is a hard problem to
solve really. You have to track the uninitialized variable usage your solve to
solve it correctly.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
GCC host triplet|mingw32 |
GCC target triplet|mingw32 |
Keywords| |diagnostic
Summary|Spurious "'<variable>' may |Spurious "'<variable>' may
|be used uninitialized in |be used uninitialized in
|this function" warnings when|this function" warnings when
|using __builtin_setjmp |using __builtin_setjmp and
| |loops and extern function
| |call
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31707