Dan Sugalski <[EMAIL PROTECTED]> wrote: > The only tricky bit comes in with the examination of the root set of > other threads--accessing the hardware register contents of another > running thread may be... interesting. (Which, I suppose, argues for > some sort of volatile marking of the temp variables)
You'll provide the "interesting" part, that is: use Psi::Estimate::CPU_Register_Changes_in_Future_till_mark_is_done; SCNR, leo
