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: -Wuninitialized issues

From: Mark Mitchell <mark at codesourcery dot com>
To: Diego Novillo <dnovillo at redhat dot com>
Cc: law at redhat dot com, "Kaveh R. Ghazi" <ghazi at caipclassic dot rutgers dot edu>, gcc at gcc dot gnu dot org
Date: Wed, 02 Nov 2005 16:43:13 -0800
Subject: Re: -Wuninitialized issues
References: <4365CA5E.3070401@codesourcery.com> <200511030004.jA304n0n022702@caipclassic.rutgers.edu> <1130977183.29507.5.camel@localhost.localdomain> <200511021929.37710.dnovillo@redhat.com>

Diego Novillo wrote:

> Agreed 100%.  My vote is to use your proposal for -Wuninitialized and have, 
> as you said, another flag that does the analysis immediately after going 
> into SSA, before any transformations are done.

It certainly doesn't bother me to have -Wuninitialized continue to mean
what it does, and have some other flag that means something else.  Or,
even -Wuninitialized=2, or something.  I think it's fine to have modes
here, and I agree that there are (clearly!) constituencies that want
both the lint-like mode and the valgrind-like mode.

Jeff, I'm sorry you're upset; I actually think we're closer to consensus
than we've ever been before on this issue. :-)

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304

Follow-Ups:
- Re: -Wuninitialized issues
  - From: Andrew Pinski
- Re: -Wuninitialized issues
  - From: Jeffrey A Law

References:
- Re: -Wuninitialized issues
  - From: Kaveh R. Ghazi
- Re: -Wuninitialized issues
  - From: Jeffrey A Law
- Re: -Wuninitialized issues
  - From: Diego Novillo

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