> I just noticed that 2.0.36 explicitly complains about gcc 2.8.x and
> requires a patch in order to be compiled by this gcc version. I took a
> look at the patch source and saw all the changes have something to do
> with assembly/machine-specific directive syntax changes and the like. It
> also has an ominous warning about the changes not having been tested.
> I already applied the patch and put everything to work, no problem. I
> just got squeamish about that warning. What could go wrong? Or can I
> sleep well at night? The machine in question is our ISP's proxy server.
There are dirty tricks in asm parts of i[3456]86 linux kernel. Since gcc 2.8.x
(and egcs) are more agressive with optimization this could lead to VERY
strange behaviour sometimes. There are NO plans to make kernel 2.0.x
gcc 2.8.x/egcs-safe. For 2.2 this goal is declared but even there some
problems still not solved. In short: if you really want to sleep well at
night use gcc 2.7.2.3, not 2.8.x or egcs even if for A LOT OF peoples patch
works Ok.
P.S. Usually problems are with X and thus will not affect your proxy server but
who knows ?
-
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/