Jeffrey A Law - Re: -Wuninitialized issues (original) (raw)
This is the mail archive of the gcc@gcc.gnu.orgmailing 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] |
- From: Jeffrey A Law
- To: Chris Lattner
- Cc: gcc at gcc dot gnu dot org, "Kaveh R. Ghazi" , dnovillo at redhat dot com, mark at codesourcery dot com
- Date: Wed, 02 Nov 2005 12:29:57 -0700
- 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>
- Reply-to: law at redhat dot com
On Wed, 2005-11-02 at 12:55 -0600, 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 think we've all agreed it's a good feature to have; I think all we're trying to work out is invocation details. ie, do we have another switch and if we do, is it enabled or disabled when the existing -Wuninitialized is enabled.
jeff
- Follow-Ups:
- Re: -Wuninitialized issues
* From: Chris Lattner
- Re: -Wuninitialized issues
- References:
- Re: -Wuninitialized issues
* From: Chris Lattner - Re: -Wuninitialized issues
* From: Jeffrey A Law - Re: -Wuninitialized issues
* From: Chris Lattner
- Re: -Wuninitialized issues
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |