On Sat, 26 Apr 2008, Ingo Molnar wrote:
quoted text
> * Gabriel C <nix.or.die@googlemail.com> wrote:
> >
> > It seems like the update triggers some compiler bug.
> > 
> > Setting CC_OPTIMIZE_FOR_SIZE=n fixed that btw.
> > 
> > I don't have the time right now but later on today I will compile 
> > gcc43_svn_branch and test again with CC_OPTIMIZE_FOR_SIZE=y and see 
> > what I get.
> > 
> > Ingo sorry for the noise.
> 
> no problem and it's not noise even if it turns out to be a compiler 
> problem - we very much want to know about them when they affect the 
> kernel.

Indeed. Often these kinds of compiler issues are also actually our bugs, 
where some code generation thing just happened to hide the fact that we 
did something wrong.

So Gabriel, it would be wondeful if you could try to pinpoint where the 
problem happens. That said, especially if you are using something like a 
self-compiled gcc from the current SVN tree, that obviously does make it a 
*lot* more likely that you are hitting a real compiler bug.

(But even then, if you can pinpoint it, I bet the gcc people would be 
really happy to hear about it.)

			Linus
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/