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

Doug Lea dl at cs.oswego.edu
Wed May 31 08:06:04 EDT 2017


On 05/31/2017 07:03 AM, Doug Lea wrote:

>>
>> C++ clearly specifies "CAS classic". There is no way to specify
>> release semantics for a failed CAS, since there is no write.
> 
> The current C++ spec, sec 29.2 includes versions that do so,

Except that memory_order_release is specifically disallowed.
Not that it matters, since the question at hand is about
volatile/seq_cst.

-Doug


More information about the Concurrency-interest mailing list