This is the mail archive of the
mailing list for the GCC project.
Re: Criteria for a warning to be in -Wall? (was: Re: a warning to implement)
- From: dewar at gnat dot com (Robert Dewar)
- To: dewar at gnat dot com, jbuck at synopsys dot COM
- Cc: galibert at pobox dot com, gcc at gcc dot gnu dot org
- Date: Thu, 7 Feb 2002 09:24:39 -0500 (EST)
- Subject: Re: Criteria for a warning to be in -Wall? (was: Re: a warning to implement)
<It seems to me that if we had an optimization level (call it -O0.5, or
just adjust -O1) in which, at the end of each line, values get flushed
back to memory, we'd pretty much have it: complicated expressions inside
one line of code could be optimized as much as you want, but the
developer in the debugger would see just what he wrote.
That sounds right, although even that may be to extreme, the debugger
can deal with local variables that live cleanly and permanently in registers.