On Wed, 2002-07-17 at 17:33, Ulrich Drepper wrote: > You will always end up with two calls to 'foo' since the compiler is not > allowed to eliminate them. It has no means to determine that 'foo' has > no side effects and a constant return value.
I'll try once more, having been seemingly ignored last time: What, precisely, is the problem with calling __error() twice?