On 4/18/07, Rana Dasgupta <[EMAIL PROTECTED]> wrote:
On 4/17/07, Mikhail Fursov <[EMAIL PROTECTED]> wrote: > On 4/18/07, Rana Dasgupta <[EMAIL PROTECTED]> wrote: > > > > Mikhail, > > I have no problem with the ones you updated, but some questions... > > > > Is VM_RT_WRITE_BARRIER_FASTCALL in use? > > > This helper is dead code today. AFAIR gcv5 uses VM_RT_GC_HEAP_WRITE_REF > today. OK thanks. We need to get rid of the dead gcv4 code. This is probably what refers to the old barrier helper. > > And are the monitor enter/exit functions all interruptible? > > > > I think monenter is must be. Thread can stall for a long period of time on > monenter. And I do not know if monexit is. At least it can throw > IllegalState-like exception in theory. Yes right, both throw exceptions like nullpointer, illegalmonitorstate etc. But these are supposed to be thrown lazily.
Actually I have never seen an exception thrown from monexit. JIT generates endless loop for an exception thrown from monexit and never let it go until monexit is called without exceptions. -- Mikhail Fursov
