This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/42884] GCC (v4.3.3) fails to detect uninitialized variable
- From: "paolo dot carlini at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Jan 2010 14:13:23 -0000
- Subject: [Bug c/42884] GCC (v4.3.3) fails to detect uninitialized variable
- References: <bug-42884-18720@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from paolo dot carlini at oracle dot com 2010-01-27 14:13 -------
I'm restating my point: indeed, the variable can be used uninitialized. This is
not at issue. My point is that, depending on the way the compiler is internally
organized, etc, you can have it warning for a larger class of cases and not
warning for a larger class of non-cases, but normally you cannot obtain full
accuracy. As two data points, for comparison, I told you that two other, up to
date, high quality, compilers don't warn either. I'm saying, do not hold your
breath on this, in principle we can, and should, make progress, but it's hard
to say now how much and when.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42884