This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Uninitialized warnings
- To: dewar at gnat dot com
- Subject: Re: Uninitialized warnings
- From: Richard Henderson <rth at redhat dot com>
- Date: Wed, 18 Jul 2001 17:11:31 -0700
- Cc: dnovillo at redhat dot com, shebs at apple dot com, amylaar at redhat dot com, carlo at alinoe dot com, dalej at apple dot com, gcc at gcc dot gnu dot org, jbuck at synopsys dot COM, kevina at users dot sourceforge dot net
- References: <20010718165504.019A1F2B45@nile.gnat.com>
On Wed, Jul 18, 2001 at 12:55:04PM -0400, dewar@gnat.com wrote:
> One request I have, and please ignore it if it has already been discussed,
> is that the uninitialized variable warning is currently very uninformative,
> since it does not indicate the site at which the uninitialized reference
> may occur, and sometimes it takes a big effort to determine why the warning
> is being issued. Is this information that can be provided?
Not with the current code.
The way this works is that we solve global data flow, and for
every variable that is live on entry to the function we check
that it is either a global register or a function argument.
Anything else gets a warning.
r~