[concurrency-interest] x86 NOOP memory barriers
nitsanw at yahoo.com
Tue Aug 6 04:38:04 EDT 2013
Summarized in this blog post here:
Please point out any mistakes/omissions/oversight.
Thanks for the help guys.
From: Michael Barker <mikeb01 at gmail.com>
To: Nitsan Wakart <nitsanw at yahoo.com>
Cc: Vitaly Davidovich <vitalyd at gmail.com>; "concurrency-interest at cs.oswego.edu" <concurrency-interest at cs.oswego.edu>
Sent: Saturday, August 3, 2013 12:33 AM
Subject: Re: [concurrency-interest] x86 NOOP memory barriers
> So because a putOrdered is a write to memory it cannot be reordered with
> other writes, as per "220.127.116.11 Neither Loads Nor Stores Are Reordered with
> Like Operations".
Yes in combination with the compiler reordering restrictions. In
Hotspot this is implemented within the
LibraryCall::inline_unsafe_ordered_store (library_call.cpp) call.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Concurrency-interest