[concurrency-interest] Suggestion: .hardGet() for atomic variables
vitalyd at gmail.com
Thu Jan 19 13:30:51 EST 2012
Volatile read does not allow subsequent operations to reorder with it - the
load must retire before subsequent reads/writes. Check Doug Lea's compiler
cookbook if you're skeptical.
I don't see what reordering you're concerned about - can you give a simple
Sent from my phone
On Jan 19, 2012 1:15 PM, "Raph Frank" <raphfrk at gmail.com> wrote:
> It doesn't have any happens before relationship with a later write.
> It is for optimistic read locks base on a sequence counter. If the
> counter hasn't changed, then there is no guarantee that that
> happens-before the counter was incremented.
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Concurrency-interest