RE: JavaMemoryModel: Specification

From: Sarita Adve (
Date: Fri Jul 13 2001 - 14:44:00 EDT

> From: Bill Pugh []
> Sent: Tuesday, July 10, 2001 7:19 PM

> What we need is the ability to contain synchronization errors, so
> that a synchronization error in one part of the program doesn't
> destroy the correctness of synchronization elsewhere in the program.

You may want to see
This paper from ISCA'91 describes a sequentially consistent semantics for
all parts of a program that are not "affected" by a data race. The "affects"
relation is in terms of happens-before. The paper gives hardware constraints
to ensure the above as well.


JavaMemoryModel mailing list -

This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:33 EDT