> In short, it may not be a technical gcc problem, but it IS a problem with
> the gcc-2.8.0 _release_. Right now it isn't entirely clear whether the
> 2.8.0 behaviour is a mistake or not, and I'm personally rather unhappy
> with people claiming that it is a Linux problem.
FYI, I digged my personal mail archives and found that I had been able to
produce bad code under similar circumstances with gcc-2.7.2.1, I have
unfortunately deleted the source example and it was 3 months ago :-(.
Gabriel.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu