I like the extra leeway so that volatile writes do not have have a single
global total order, but only those orderings obviously required, which Bill
enumerated. I think it may have bearing on concurrent copying garbage
collectors, which may need to solve the problem of moving a volatile field
from on place to another while non-gc threads are accessing it. This may
stretch the action out more in time, and give another source of two copies,
that different threads might access (but which cannot be updated atomically
at the hardware level on most machines).
Regards -- Eliot
==============================================================================
J. Eliot B. Moss, Associate Professor http://www.cs.umass.edu/~moss www
Department of Computer Science +1-413-545-4206 voice
140 Governor's Drive, Room 372 +1-413-545-1249 fax
University of Massachusetts moss@cs.umass.edu email
Amherst, MA 01003-9264 USA +1-413-545-3733 Priscilla Coe sec'y
==============================================================================
-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel
This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:37 EDT