| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8258542 | 17 | Maurizio Cimadamore | P3 | Resolved | Fixed | b03 |
The Foreign Memory Access API supports several kind of segments:
* off-heap (base == null)
* on-heap (base == X[]), for each primitive X (except boolean)
If static accessor methods in MemoryAccess are called repeatedly with different segment kinds, optimizations of unsafe access are lost and performance degrades significantly.
Same issue occurs when memory access var handles are used directly.
* off-heap (base == null)
* on-heap (base == X[]), for each primitive X (except boolean)
If static accessor methods in MemoryAccess are called repeatedly with different segment kinds, optimizations of unsafe access are lost and performance degrades significantly.
Same issue occurs when memory access var handles are used directly.
- backported by
-
JDK-8258542 Type profile pollution occurs when memory segments of different kinds are used
-
- Resolved
-
