Re: GCC 3.3.2 -Wall affects the code generated...

Denis Zaitsev wrote:
> header an inline function named strip is defined.  And I found that
> the object code generated for this function depends of the presence of
> -Wall in the list of option to GCC.  

This is probably a bug.  This is a small loop that is being complied 
differently, so this might be a problem with a loop optimizer, or with 
the basic block reorganizer.  I'd guess we have an uninitialized 
variable, or some other kind of memory corruption somewhere.  I don't 
know of any other reason why -Wall would effect the code emitted.

We need a testcase to look at this.  The source you provided can not be 
compiled on its own.  I don't happen to have an x86 GLIBC tree, so I can 
not easily generate my own testcase.  I tried fixing your testcase to 
make it compilable, but nothing interesting happens when using 
gcc-3.3.4.  I suspect that there is a complicated interaction going on 
here, and we actually need the full input file to reproduce the problem, 
rather than just the source for the one function that changes.  Or maybe 
the problem has already been fixed.  I can't tell.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com