[Bug middle-end/50950] warning missed when OR'ing to an uninitialized variable

2011-11-02 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50950 --- Comment #1 from Richard Guenther rguenth at gcc dot gnu.org 2011-11-02 09:48:16 UTC --- No, it's the lame warning-for-uninitialized-memory (your variables are address-taken) code that triggered in 4.4 but not in newer releases. Thus it's more

[Bug middle-end/50950] warning missed when OR'ing to an uninitialized variable

2011-11-02 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50950 Richard Guenther rguenth at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug middle-end/50950] warning missed when OR'ing to an uninitialized variable

2011-11-02 Thread sezeroz at gmail dot com
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: