🚀 go-pugleaf

(Using GCC 2.7.0)

I'm not sure if this is considered a bug.

When optimizing a program containing vfork() or longjmp(), GCC often 
registerizes variables and then complains that they will be 
clobbered. (fortunately on my system vfork() is actually fork(), so I 
don't need to work)

I think correct behavior would be for GCC to consider vfork() and 
longjmp() before it registerizes variables.

I'd also suggest adding some new flags (say -fsafe-longjmp, 
-fsafe-vfork). One state would be used for OSes with "safe" vfork() 
and longjmp(), in which case these warnings would be suppressed, and 
in the other state the compiler would un-registerize the variables 
and prevent the problem. Of course the "clobber" warning would 
persist when using stupid register allocation.

---- Michael Deutschmann <ldeutsch@netshop.net>