-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 13
-
b09
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8234564 | 11.0.7-oracle | Vladimir Ivanov | P4 | Resolved | Fixed | b01 |
JDK-8229973 | 11.0.5 | Vladimir Ivanov | P4 | Resolved | Fixed | b05 |
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.
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.
- backported by
-
JDK-8229973 Keep track of memory accesses originated from Unsafe
- Resolved
-
JDK-8234564 Keep track of memory accesses originated from Unsafe
- Resolved