another possible fix is to declare conv_res as volatile. It
will still be gc protected if it's on the stack and not in a
register, right?
declaring it volatile forces the compiler to keep it on the
stack, not in a register, so the value won't ever be
eliminated by live-range analysis.
rrrr. finding other occurrences of this type of problem is
nontrivial. it can happen whenever you construct a scheme
object as a temporary holder for non-scheme objects.
--
Received on Thu Apr 06 2000 - 14:10:23 CEST