public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: Andrew Thomas Pinski <pinskia@gmail.com> To: "gcc-bugzilla@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org> Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org> Subject: Re: [Bug c/38961] if () block not true but a command in it is still in effect Date: Sat, 24 Jan 2009 22:33:00 -0000 [thread overview] Message-ID: <32CDCAFA-A097-4D49-A954-92C12C16A263@gmail.com> (raw) In-Reply-To: <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 >
next prev parent reply other threads:[~2009-01-24 22:33 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-24 17:36 [Bug c/38961] New: " jellegeerts at gmail dot com 2009-01-24 17:48 ` [Bug c/38961] " falk at debian dot org 2009-01-24 18:15 ` jellegeerts at gmail dot com 2009-01-24 18:19 ` rguenth at gcc dot gnu dot org 2009-01-24 18:45 ` jellegeerts at gmail dot com 2009-01-24 19:37 ` rguenth at gcc dot gnu dot org 2009-01-24 22:25 ` jellegeerts at gmail dot com 2009-01-24 22:33 ` Andrew Thomas Pinski [this message] 2009-01-24 22:33 ` pinskia at gmail dot com 2009-01-25 1:50 ` jellegeerts at gmail dot com 2009-01-25 1:54 ` jellegeerts at gmail dot com 2009-01-25 11:15 ` rguenth at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=32CDCAFA-A097-4D49-A954-92C12C16A263@gmail.com \ --to=pinskia@gmail.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-bugzilla@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).