Re: [Sablevm-developer] Threading support in SableVM

[Chris P. <chr...@ma...>]

Clark VERBRUGGE wrote:

> That would fix the java heap.  But are not internal sablevm operations
> more of the problem?  Are all shared data accesses (reads or writes)
> already protected by mutexes?

I didn't answer your question.  The answer is I think so, but I don't 
know.  I think certain things are declared as volatile so that explicit 
mutexes aren't required, but that this may be broken.  There might be 
problems with both thin locks and the thread status variable, amongst 
other things.  We'll see ... I think the first step is to make the Java 
heap work.  After that we can try to break things again.

Cheers,
Chris