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: "rguenth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Jan 2010 19:51:41 -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 #18 from rguenth at gcc dot gnu dot org 2010-01-27 19:51 -------
(In reply to comment #17)
> (In reply to comment #16)
> > No, it's an implementation detail. Uninitialized variable use tracking
> > works with detecting uses of SSA name default definitions. Memory
> > is not in SSA form so this mechanism does not work.
> >
> > Uninitialized memory detection is not done at all.
> >
>
> Forgive me for I know not much of the GCC internals (I use GCC, I don't develop
> it), but are you saying that any use of address-of on a variable kicks it out
> of contention for unused tracking? Even if it's not on a direct path (e.g.,
> not always executed)?
Yes, that's correct.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42884