RFR(s): 8191859: SoftReference clock/timestamp should be declared volatile
per.liden at oracle.com
Fri Nov 24 13:13:47 UTC 2017
The clock and timestamp fields in SoftReference should be declared
volatile. These fields are read or updated by the VM, (possibly)
concurrently with the execution of Java threads.
To be more specific, the timestamp field is read by the GC during
reference discovery, e.g. during G1/CMS concurrent mark. The clock is
updated by the GC, typically after reference processing has completed.
More information about the core-libs-dev