2.0 it wont - the problem isnt egcs, if it was egcs it would be simple.
The problem is generally egcs being _too_ good at its job
Its quite happy to rearrange the order of operations for performance and
to remove "dead code". Of course the former when not correctly marked in
device drivers is a disaster and the latter tends to include little things
like delay loops that have been handled wrongly.
For 2.1.x we are trying to cover all of these, for 2.0.x its not a good
plan to even attempt it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu