This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: [Bug c/38961] if () block not true but a command in it is still in effect
- From: Andrew Thomas Pinski <pinskia at gmail dot com>
- To: "gcc-bugzilla at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- Cc: "gcc-bugs at gcc dot gnu dot org" <gcc-bugs at gcc dot gnu dot org>
- Date: Sat, 24 Jan 2009 14:33:08 -0800
- Subject: Re: [Bug c/38961] if () block not true but a command in it is still in effect
- References: <bug-38961-16461@http.gcc.gnu.org/bugzilla/> <20090124222454.29966.qmail@sourceware.org>
Sent from my iPhone
On Jan 24, 2009, at 2:24 PM, "jellegeerts at gmail dot com" <gcc-bugzilla@gcc.gnu.org
> wrote:
------- Comment #6 from jellegeerts at gmail dot com 2009-01-24
22:24 -------
Seems reasonable, though I'd vote for -Wall to include -Winit-self.
I actually discovered this because of a bug I found in lxpanel. Now
of course
it's the fault of those developers not to use -Winit-self, but seen
the other
options that -Wall enables, it seems reasonable to also enable -
Winit-self.
Except -Winit-self is there because we decided a long time ago initing
the variable by itself is a way to disable the uninitization warning.
In fact before 3.4 there was no way to get this warning (oh I added
this option:) ).
Thanks,
Andrew Pinsky
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38961