This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/68641] undefined variables implicitly considered to be zero
- From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 02 Dec 2015 12:03:50 +0000
- Subject: [Bug rtl-optimization/68641] undefined variables implicitly considered to be zero
- Auto-submitted: auto-generated
- References: <bug-68641-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68641
--- Comment #10 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
(In reply to rguenther@suse.de from comment #9)
> Though with the testcase you gave we warn at both -O0 and -O1:
yes, but unfortunately, -Wuninitialized, also warns for 'may be used
uninitialized' which are too often false positives, and sometimes even compiler
generated variables as in PR67679.
A -Wmust-be-uninitialized (which seemingly the compiler could do as the comment
on top of init-regs.c suggests) would be valuable. [I just checked that
-Wuninitialized -Wno-maybe-uninitialized doesn't work]