This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.4/4.6/4.7 uninitialized warning regression?
- From: Cary Coutant <ccoutant at google dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: GCC Development <gcc at gcc dot gnu dot org>, Xinliang David Li <davidxl at google dot com>
- Date: Wed, 20 Apr 2011 12:03:18 -0700
- Subject: Re: GCC 4.4/4.6/4.7 uninitialized warning regression?
- References: <BANLkTimGpE8y3EDBy9VLATv5d_+GU31=wA@mail.gmail.com>
> This brings out 2 questions. ?Why don't GCC 4.4/4.6/4.7 warn it?
> Why doesn't 64bit GCC 4.2 warn it?
Good question. It seems that the difference is whether the compiler
generates a field-by-field copy or a call to memcpy(). According to
David, the trunk gcc in 32-bit mode doesn't call memcpy, but still
doesn't warn. He's looking at it.
-cary