[jmm-dev] Specifying VarHandle acquire/release without ill effects

Martin Buchholz martinrb at google.com
Tue Jun 28 01:05:40 UTC 2016

On Mon, Jun 27, 2016 at 5:20 PM, Hans Boehm <boehm at acm.org> wrote:

> I would probably define synchronization actions to include acquire and
> release operations, and rename synchronization order to something else (SC
> order?), and ensure that it includes only SC operations.  That's what C++
> currently does, effectively.

Reading the C++ standard, I see:
- they use "synchronization operations" instead of "synchronization
actions".  We should adopt the former, incorporating the release/acquire
operations as they do.
- they don't have a real name for "synchronization order"; they just give
it a temporary name """There shall be a single total order S on all
memory_order_seq_cst operations"""

More information about the jmm-dev mailing list