OK, we're going to have to adjust this.
Jeremy, Sarita and I are working on something, give us another day
or so to sanity check it.
The intent is still the same:
* Not require any thread scheduling fairness
* Prevent transformations such as hoisting
a volatile read out of a loop (in the general
case).
Bill
-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel
This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:01:03 EDT