http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18016
--- Comment #14 from ejb at ql dot org 2011-06-27 18:06:15 UTC ---
Very nice to see this bug fixed. :-)
at gcc dot gnu dot org
ReportedBy: ejb at ql dot org
CC: ejb at ql dot org,gcc-bugs at gcc dot gnu dot org
GCC build triplet: i486-linux
GCC host triplet: i486-linux
GCC target triplet: i486-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18016
--- Additional Comments From ejb at ql dot org 2004-10-15 16:46 ---
Created an attachment (id=7358)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=7358action=view)
source file that reproduces problem
This attachment contains the code that is also inlined in the bug report
Priority: P2
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: ejb at ql dot org
CC: ejb at ql dot org,gcc-bugs at gcc dot gnu dot org
GCC build triplet: any
GCC host triplet: any
GCC target triplet: any
http://gcc.gnu.org
--- Additional Comments From ejb at ql dot org 2004-10-15 20:34 ---
I think you misunderstood. I'm not suggesting -Wunitialized should turn on
-Winit-self; I'm suggesting the other way around. Since -Winit-self doesn't
work without -Wunitialized, it's pointless to have it without
--- Additional Comments From ejb at ql dot org 2004-10-15 20:40 ---
In other words, instead of saying:
Note this option can only be used with the`-Wuninitialized' option, which in
turn only works with `-O1' and above.
say
Note this option automatically implies -Wunitialized, which
