RFR: 8314480: Memory ordering spec updates in java.lang.ref [v25]

[Viktor Klang]

On Wed, 24 Apr 2024 23:15:45 GMT, Brent Christian <bchristi at openjdk.org> wrote:

>> Classes in the `java.lang.ref` package would benefit from an update to bring the spec in line with how the VM already behaves. The changes would focus on _happens-before_ edges at some key points during reference processing.
>> 
>> A couple key things we want to be able to say are:
>> - `Reference.reachabilityFence(x)` _happens-before_ reference processing occurs for 'x'.
>> - `Cleaner.register()` _happens-before_ the Cleaner thread runs the registered cleaning action.
>> 
>> This will bring Cleaner in line (or close) with the memory visibility guarantees made for finalizers in [JLS 17.4.5](https://docs.oracle.com/javase/specs/jls/se18/html/jls-17.html#jls-17.4.5):
>> _"There is a happens-before edge from the end of a constructor of an object to the start of a finalizer (§12.6) for that object."_
>
> Brent Christian has updated the pull request incrementally with one additional commit since the last revision:
> 
>   package spec updates, mostly about reference queues and dequeueing

src/java.base/share/classes/java/lang/ref/package-info.java line 153:

> 151:  * <li> The enqueueing of a reference (by the garbage collector, or
> 152:  * by a successful call to {@link Reference#enqueue}) <i>happens-before</i>
> 153:  * the reference is removed from the queue (<em>dequeued</em>).</li>

@bchristi-git I wonder if it makes sense to use the same style when referring to "dequeue", so either always within quotes or only using <em>em</em> (see line 108)

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/16644#discussion_r1579082626