Probably a bug
Andrew Haley
aph at redhat.com
Wed Feb 19 12:40:22 UTC 2020
On 2/19/20 12:29 PM, Aleksey Shipilev wrote:
> Unsafe.putOrderedObject is releasing store in Unsafe newspeak.
Oh, so it is. OK.
> You are probably confusing it with opaque.
No, I made the mistake of reading the description, which doesn't seem to help:
* Version of {@link #putObjectVolatile(Object, long, Object)}
* that does not guarantee immediate visibility of the store to
* other threads. This method is generally only useful if the
* underlying field is a Java volatile (or if an array cell, one
* that is otherwise only accessed using volatile accesses).
I didn't spot this:
* Corresponds to C11 atomic_store_explicit(..., memory_order_release).
--
Andrew Haley (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
More information about the shenandoah-dev
mailing list