[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc
Subject:    Re: gcc and the kernel
From:       Andi Kleen <andi () firstfloor ! org>
Date:       2008-12-30 8:33:09
Message-ID: 87ocyuukoq.fsf () basil ! nowhere ! org
[Download RAW message or body]

"Brian O'Mahoney" <omb@bluewin.ch> writes:
>
> Last, a word to the wise, compiler developers, are by nature fairly agressive 
> but, unless you want to work on gcc itself, it is wise to stay a bit behind 
> the bleeding edge, and, unless your systems are excellently backed up,
> ___DONT_BUILD_THE_KERNEL___ with and untested gcc. I mean a kernel you are 
> going to try to run. For an example of why not see the 'ix68 string 
> direction' fiasco noting that an interrupt can happen anywhere and that the 
> CPU x flag is a non-deterministic (to the interrupt code) part of the 
> interrupted context. Oh what fun!

This particular problem has nothing to do with the compiler that built the
kernel.

-Andi
-- 
ak@linux.intel.com
[prev in list] [next in list] [prev in thread] [next in thread]