[concurrency-interest] Concurrency-interest Digest, Vol 73, Issue 15
dl at cs.oswego.edu
Thu Mar 3 07:01:28 EST 2011
On 03/03/11 02:57, Mohit Kumar wrote:
> This means(theoretically) in a NON Hotspot jvm the guarantees provided by the
> atomic classes wont break
> even if the NON Hotspot JVM doesn't apply those additional barriers because the
> variable is declared volatile.
> (I understand that x86/sparc CAS has the required ordering but what about Power
Mappings of compareAndSet etc on all platforms must obey the same specs.
So for example, on Power and ARM, the compareAndSet method issues
barriers in addition to an LL/SC. We are in regular contact with VM
and processor spec folks to help ensure that these are done correctly.
More information about the Concurrency-interest