Re: v4.10: kernel stack frame pointer .. has bad value (null)
From: Pavel Machek
Date: Thu Mar 09 2017 - 16:12:42 EST
On Thu 2017-03-09 16:29:10, Peter Zijlstra wrote:
> On Wed, Mar 08, 2017 at 10:22:53PM +0100, Pavel Machek wrote:
> > Well, I have fast CPUs, but most of the time they just compile
> > stuff. Especially bisect is compile-heavy. I suspect going back to
> > gcc-3.2 would bring me bigger advantages than CPU upgrade...
> But note that 3.2 compiles a distinctly different kernel from something
> new and shiny. The kernel uses a lot of GCC features optimistically to
> generate different code.
> So if by some chance your error depends on one of the new features,
> bisecting with some ancient compiler will not work.
Well, yes, obviously different compilers generate different code.
OTOH for drivers (where most errors are) the difference should not be
And actually.. if you realize it bug is gcc version dependend, you'll
know where to look for the bug.
(Anyway, it looks like gcc-3.3 is not usable for kernel on x86, and it
is actually slower, too. So -- bad idea. gcc -O1 looks promising.)
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Description: Digital signature