Re: v4.10: kernel stack frame pointer .. has bad value (null)
From: Peter Zijlstra
Date: Thu Mar 09 2017 - 10:30:26 EST
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.
And I cannot see that getting any better, only worse.