RE: JavaMemoryModel: Ordering of volatile and monitor actions

From: Sarita Adve (sadve@cs.uiuc.edu)
Date: Fri Jun 29 2001 - 18:38:29 EDT


> -----Original Message-----
> From: owner-javamemorymodel@cs.umd.edu
> [mailto:owner-javamemorymodel@cs.umd.edu]On Behalf Of Bill Pugh
> Sent: Thursday, June 28, 2001 8:36 AM
> To: Joseph Bowbeer
> Cc: javamemorymodel@cs.umd.edu
> Subject: Re: JavaMemoryModel: Ordering of volatile and monitor actions
>

>
> Reordering a monitorexit and a finite number of volatile reads may
> fall into the category of something that is illegal in the semantics,
> but can't be observed so is legal in the implementation.

This really should not be an issue. The *semantics* should be specified in a
way that all implementations are legal. (Hence the previous suggestion of
giving up on per-process orderings as a way to specify the semantics.)

Sarita

-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel



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