Re: strange optimisation behaviour

[Gav Wood]

> You should always (a) suspect your own code before you suspect the
> compiler/runtime libraries/OS etc.
>
> Anything is a likely suspect, but your code is the likeliest
> of all.

found it.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9993

i was using 3.2.2 on my release machine, which is completely broken for the
structure i was using (infinite loop with a qualified return and internal
stack based variables).

as if it could by my code that's wrong :-)

gav

-- 
Gav Wood
University of York