"Khimenko Victor" <email@example.com> said:
> It's other way around. If RELEASED gcc miscompiles kernel it's kernel
> problem (BTW I've using gcc 2.95 compiled 2.2.x kernels for last year
> without problems) . If UNSTABLE gcc miscompiles kernel then it's not
> even kernel issue ...
Sorry to interrupt, but unless you take a careful look you just can't
know if gcc or the kernel is/are to blame. In this case, there are
indications that (again!) it is the kernel code making unwarranted
assumptions about gcc's optimizations.
In any case, it has to be checked: Someday the current unstable gcc _will_
be the released version. Then what? Tell people to use the old, severely
broken 220.127.116.11 again?
-- Horst von Brand firstname.lastname@example.org Casilla 9G, Vin~a del Mar, Chile +56 32 672616
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Aug 07 2000 - 21:00:07 EST