-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
Certain access mode methods have api notes stating compatible memory ordering effects with C++ atomics.
Similar api notes can be added to other access mode methods:
On Fri, Apr 8, 2016 at 7:40 AM, Aleksey Shipilev
<aleksey.shipilev@oracle.com> wrote:
On 04/08/2016 03:51 PM, Paul Sandoz wrote:
http://cr.openjdk.java.net/~psandoz/jdk9/JDK-8151198-VH-factory-exceptions/webrev/
<http://cr.openjdk.java.net/~psandoz/jdk9/JDK-8151198-VH-factory-exceptions/webrev/>
I agree with updates.
But have more comments on C/C++ @apiNote-s. Would you like to address
them in follow-ups? Notably, getVolatile may be also marked analogous to
memory_order_seq_cst, and get/setOpaque may be marked analogous to C/C++
"volatile"-s. And CAS/CAE memory semantics can also be spelled out in
terms of std::memory_order.
Similar api notes can be added to other access mode methods:
On Fri, Apr 8, 2016 at 7:40 AM, Aleksey Shipilev
<aleksey.shipilev@oracle.com> wrote:
On 04/08/2016 03:51 PM, Paul Sandoz wrote:
http://cr.openjdk.java.net/~psandoz/jdk9/JDK-8151198-VH-factory-exceptions/webrev/
<http://cr.openjdk.java.net/~psandoz/jdk9/JDK-8151198-VH-factory-exceptions/webrev/>
I agree with updates.
But have more comments on C/C++ @apiNote-s. Would you like to address
them in follow-ups? Notably, getVolatile may be also marked analogous to
memory_order_seq_cst, and get/setOpaque may be marked analogous to C/C++
"volatile"-s. And CAS/CAE memory semantics can also be spelled out in
terms of std::memory_order.