This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Google SoC Project Proposal: Better Uninitialized Warnings

From: Robert Dewar <dewar at adacore dot com>
To: law at redhat dot com
Cc: Manuel López-Ibáñez <lopezibanez at gmail dot com>, GCC <gcc at gcc dot gnu dot org>, Ian Lance Taylor <iant at google dot com>, Diego Novillo <dnovillo at redhat dot com>
Date: Mon, 19 Mar 2007 09:07:27 -0400
Subject: Re: Google SoC Project Proposal: Better Uninitialized Warnings
References: <6c33472e0703171128q3dff544dydd6ab16fe4a67323@mail.gmail.com> <1174288422.5239.60.camel@sweet.slc.redhat.com>

Jeffrey Law wrote:

The one technical bit we never tacked was unoptimized compilation; I
goof'd at one time and thought we went ahead and build the SSA graph
even when not optimizing which is incorrect.  I don't think fixing this
should be a requirement for improving the current situation with
-Wuninitialized, but if you've got the time, investigation would be
a great bonus.


I agree this would be helpful. One of the reasons that the GNAT
front end has its own circuits to detect some cases of uninitialized
variables is to get these warnings even with no optimization.

Jeff

Follow-Ups:
- Re: Google SoC Project Proposal: Better Uninitialized Warnings
  - From: Manuel López-Ibáñez

References:
- Google SoC Project Proposal: Better Uninitialized Warnings
  - From: Manuel López-Ibáñez
- Re: Google SoC Project Proposal: Better Uninitialized Warnings
  - From: Jeffrey Law

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]