-
Enhancement
-
Resolution: Fixed
-
P4
-
23
-
b20
Unsafe::setMemory is for instance used to zero out native MemorySegments when they are allocated.
Currently it only has a native implementation in unsafe.cpp, meaning that we do 2 thread state transitions on every call (Java -> native and native -> VM).
By intrinsifying this method in C2 (as a leaf call), we could avoid both state transitions which should yield significant speedups for small fill sizes.
Currently it only has a native implementation in unsafe.cpp, meaning that we do 2 thread state transitions on every call (Java -> native and native -> VM).
By intrinsifying this method in C2 (as a leaf call), we could avoid both state transitions which should yield significant speedups for small fill sizes.
- relates to
-
JDK-8331033 EA fails with "EA unexpected CallLeaf unsafe_setmemory" after JDK-8329331
-
- Closed
-
-
JDK-8333677 Improve Unsafe::setMemory intrinsics
-
- Open
-
-
JDK-8351140 RISC-V: Intrinsify Unsafe::setMemory
-
- Open
-
-
JDK-8330821 Rename UnsafeCopyMemory
-
- Resolved
-
(1 links to)