This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/41817] bogus "may be uninitialized" (huge testcase, inlining?)
- From: "manu at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Nov 2009 12:19:59 -0000
- Subject: [Bug middle-end/41817] bogus "may be uninitialized" (huge testcase, inlining?)
- References: <bug-41817-18353@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from manu at gcc dot gnu dot org 2009-11-19 12:19 -------
This is still unconfirmed until someone looks at the dumps and check that the
variables are indeed initialized in all paths that can be sensibly detected by
GCC.
BTW, when you release code, your compiler flags should not contain -Werror. If
some package does, you should really report it upstream because taking into
account all the amount of new warnings, and fixes to existing warnings that
occur between consecutive GCC releases, that is madness for any user compiling
your code.
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu dot org
OtherBugsDependingO| |24639
nThis| |
Summary|elfutils fails with "may be |bogus "may be uninitialized"
|uninitialized" with -O3 - |(huge testcase, inlining?)
|mtune=k8 |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41817