[concurrency-interest] x86 NOOP memory barriers
mikeb01 at gmail.com
Fri Aug 2 18:33:33 EDT 2013
> 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.
More information about the Concurrency-interest