This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/50950] warning missed when OR'ing to an uninitialized variable
- From: "sezeroz at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 02 Nov 2011 11:29:20 +0000
- Subject: [Bug middle-end/50950] warning missed when OR'ing to an uninitialized variable
- Auto-submitted: auto-generated
- References: <bug-50950-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50950
--- Comment #3 from Ozkan Sezer <sezeroz at gmail dot com> 2011-11-02 11:29:20 UTC ---
(In reply to comment #2)
> A dup actually (fixed on trunk):
>
Thank you. Can we expect a backport of the fix to 4.5 and 4.6?
> t.c: In function 'f0':
> t.c:14:5: warning: 'x' is used uninitialized in this function [-Wuninitialized]
> t.c: In function 'f1':
> t.c:22:11: warning: 'x.i32.i' is used uninitialized in this function
> [-Wuninitialized]
> t.c: In function 'ff1':
> t.c:30:5: warning: 'x' is used uninitialized in this function [-Wuninitialized]
> t.c: In function 'ff2':
> t.c:40:11: warning: 'y.i32.i' is used uninitialized in this function
> [-Wuninitialized]
>
> even better than for 4.4.
Hmm, the warning is still selectively emitted only for the first uninitialized
variable, though.