[Bug c/42884] GCC (v4.3.3) fails to detect uninitialized variable

["tstdenis at elliptictech dot com" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #7 from tstdenis at elliptictech dot com  2010-01-27 14:28 -------
(In reply to comment #6)
> 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.


I take your point about false warnings, but if something like coverity can
correctly identify this, it is possible.  I wouldn't expect this to be fixed
overnight, but part of the point is to at least report these things so
developers know about them.


-- 

tstdenis at elliptictech dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|4.3.3                       |unknown


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42884