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: Neil Booth <neil at daikokuya dot co dot uk>
To: Chris Lattner <sabre at nondot dot org>
Cc: Jeffrey A Law <law at redhat dot com>, gcc at gcc dot gnu dot org, "Kaveh R. Ghazi" <ghazi at caipclassic dot rutgers dot edu>, dnovillo at redhat dot com, mark at codesourcery dot com
Date: Thu, 3 Nov 2005 08:26:52 +0900
Subject: Re: -Wuninitialized issues
References: <Pine.LNX.4.61.0511021147580.14971@nondot.org> <1130957379.19967.507.camel@localhost.localdomain> <Pine.LNX.4.61.0511021253520.14971@nondot.org>

Chris Lattner wrote:-

> >I think it's worth noting that we build the SSA form even when we're
> >not optimizing.  Which in turn with running the maybe-uninitialized
> >warning code early would give you the warnings you expect without
> >needing to run the optimizers.  That's why I don't think we need to push
> >these warnings into the front-ends.
> 
> Sure, running it as the first stage of the optimizers has the effect of 
> making it have the properties I desire, without requiring the front-ends 
> to duplicate the code.  Such a feature would be great to have!

I agree if it's run with -fsyntax-only; IMO this flag should pick up
the obvious cases.

Neil.

References:
- Re: -Wuninitialized issues
  - From: Chris Lattner
- Re: -Wuninitialized issues
  - From: Jeffrey A Law
- Re: -Wuninitialized issues
  - From: Chris Lattner

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