Rename UnsafeCopyMemory to UnsafeMemoryAccess. This will make it more clear since Unsafe::setMemory and fill routines also use this scheme.
This was going to be done withinJDK-8329331 but it was recommended that it be moved to a separate issue.
This was going to be done within
- relates to
-
JDK-8329331 Intrinsify Unsafe::setMemory
- Resolved