This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/38961] if () block not true but a command in it is still in effect
- From: "jellegeerts at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Jan 2009 01:54:45 -0000
- Subject: [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/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #9 from jellegeerts at gmail dot com 2009-01-25 01:54 -------
Never mind my last message, misunderstood something.
Andrew, you say -Winit-self was added because initing a var by itself was a way
to disable the -Wuninitialized warning, but shouldn't -Wuninitialized itself
warn about the -Winit-self case? In the end it's still undefined behavior and
it makes little sense to allow it (correct me if you have other ideas).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38961