🚀 go-pugleaf

On 8 Aug 1996 21:51:37 +0100, guenter@castle.dinoco.de (Heinz Guenter
Scharf) wrote in comp.lang.c:


=>I have had a look at the assembler output of the optimized and the
unoptimized
=>compiler run. The optimization puts the flag into a register and
tests if it is
=>zero, the non optimized versions look into the stackmemory, so if
the signal-
=>routine changes the contents of the memory, the optimized version
doesn't
=>notify anything. The calling of an external function forces the
compiler to
=>reload the contents of the flag because the compiler cannot assume,
that the
=>register sare all saved. A solution could be to create a sourcefile
with a dummy
=>function with a parameter, or to disable temporarely the
optimization.

Why not just use the keyword 'volatile' ? Does gcc not support it?
(pardon me - I don't [currently] use gcc).