Integrated: 8314294: Unsafe::allocateMemory and Unsafe::freeMemory are slower than malloc/free

[David Holmes]

On Fri, 29 Sep 2023 06:48:05 GMT, David Holmes <dholmes at openjdk.org> wrote:

> To increase performance by avoiding a thread-state transition (native -> in_vm) we change the three "raw" allocation functions in Unsafe to be UNSAFE_LEAF rather than UNSAFE_ENTRY.
> 
> It is hard to track through all the related code to prove this is a safe change, but I could not spot anything obvious and testing indicated no issues (my main concern was potential missing WXWrite on macOS Aarch64).
> 
> Testing:
>   - tiers 1-7 on linux and macos x64 and Aarch64, plus Windows x64
> 
> Thanks

This pull request has now been integrated.

Changeset: 26c21f50
Author:    David Holmes <dholmes at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/26c21f50a39a4ae0425b6e7ae63afbdaf627e710
Stats:     3 lines in 1 file changed: 0 ins; 0 del; 3 mod

8314294: Unsafe::allocateMemory and Unsafe::freeMemory are slower than malloc/free

Reviewed-by: shade, dlong

-------------

PR: https://git.openjdk.org/jdk/pull/15977