This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/13959] un-init local variable detection enhancement request
- From: "dhazeghi at yahoo dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Feb 2004 02:52:38 -0000
- Subject: [Bug c++/13959] un-init local variable detection enhancement request
- References: <20040201141801.13959.d.binderman@virgin.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From dhazeghi at yahoo dot com 2004-02-02 02:52 -------
While I see your point, the fact is that in gcc -O0 means no optimization _whatsoever_. There are
many people who are quite upset (rightly IMO) about gcc compilation speed as it is, and slowing
down the default will hardly help.
We try very hard to avoid false positives. This is the primary reason why that 'might' is there.
Have you looked at the thread Andrew mentioned in the other PR (11182)? If you're still of the
same opinion after reading that, then perhaps you can open a new enhancement request
specifically for the issue of "certainty".
And not to sound pessimistic, but we have enough code-generation bugs at this point, that
enhancements tend to be a function of somebody being interested enough to write the code...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13959