JDK-8218879 : Keep track of memory accesses originated from Unsafe
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 11,13
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-02-12
  • Updated: 2019-11-21
  • Resolved: 2019-02-14
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11 JDK 13
11.0.5Fixed 13 b09Fixed
Description
It's useful to differentiate between memory accesses originated from bytecode and Unsafe usages.  

While JVM performs access checks for field accesses and range checks for array accesses, it's user responsibility to perform all necessary checks to ensure safety when it comes to Unsafe. 

From compiler perspective, it may be useful to distinguish between those.
Comments
Fix Request (11u) Provides required infrastructure for subsequent compiler backports (for example JDK-8224658). Patch does not apply cleanly to 11u due to context changes. Patched version passes tier1, tier2. 11u RFR: https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-August/001598.html
07-08-2019