[concurrency-interest] AtomicReference.updateAndGet() mandatory updating

Andrew Haley aph at redhat.com
Sat May 27 02:39:03 EDT 2017

On 26/05/17 21:08, Nathan and Ila Reynolds wrote:
> Does memory effects mean the cache line will be switched into the 
> modified state even if an actual write doesn't occur?  Or does memory 
> effects have to do with ordering of memory operations with respect to 
> the method's operation?

Cache line states aren't visible to a program, so all we can see
are ordering relationships between reads and writes.

Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the Concurrency-interest mailing list