"Simon J. Gerraty" wrote:

> I can modify the code so that interesting vars are not buried within
> narrow contexts where they are hard to access, but is there a reliable
> way to stop gcc optimizing them away?

-O0 should make it spit out really slow code with no optimisitions at
all.  'Tis almost fun comparing the output of "cc -S -O0" and "cc -S -O2"
for even the simplist function...

Simon.