|> On Thu, 17 Jun 1999, Horst von Brand wrote:
|>
|> > It just so happens that the kernel is _the_ code that most streches the
|> > compiler, AFAIK. Breakage due to ill-understood features, usage of outright
|> > compiler bugs and reliance on optimizations done a certain way (or not
|> > done) does happen.
|>
|> I believe that the compiler itself is a larger code base, but it likely
|> doesn't have as much hack work in it. :-)
The gcc source does not stress the compiler as much as the linux kernel
source. At least the C part of gcc is written in a way that even some
broken compilers still generate non-broken code. This is not so much the
case with the other backends, since they are expected to be compiled with
gcc (after the bootstrap pass has finished).
-- Andreas Schwab "And now for something schwab@issan.cs.uni-dortmund.de completely different" schwab@gnu.org- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/