This is the mail archive of the
mailing list for the GCC project.
Re: Odd gcc-6.3.0 code generation on mips64 platform causing kernel Oops
On 23/01/17 16:11, Joshua Kinard wrote:
> So now the question is why stack-probing kills this machine on generic MIPS
> code that its smaller cousin is seemingly unaffected by. I do know that IP27
> has a different set of memory initialization routines in the MIPS code, so is
> it possible that, at the point that _raw_spin_lock_irq is called and the
> stack-probe happens, that there isn't any stack space available because the
> IP27-specific memory init hasn't yet completed?
I'm sorry, but that really is a question for the kernel people.