Note that it's likely that there is just a few places (or even just _one_)
where Linux and egcs disagree about something. So it can be very setup-
dependent, and it could also be a question of timing.
For example, it could be a case where egcs actually does something that is
correct ANSI C - re-orders stores to different memory locations because
egcs did the alias analysis and determined that they cannot clash. And it
may be that the kernel depends on the exact order of stores. That would be
a kernel bug.
Equally possible is that egcs just gets the alias calculations wrong, or
that there is some other bug that just makes it generate bad code under
certain circumstances. Finding out exactly what the problem is can be
_very_ hard: the oops that was posted looked basically like memory
corruption, so the bug was not actually likely to be anywhere close to
where the crash actually happened.
Linus
-
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/