Our ongoing audit flags that newly added code (and recently modified by [JDK-8394802](https://bugs.openjdk.org/browse/JDK-8394802)) in Unsafe lacks @ForceInline, like some of their siblings do. It is both a code discipline issue, and potential performance roadbump if we somehow decide not to inline through these methods.
I marked methods that AFAICS end up calling `@IntrinsicCandidate`, so forcing inlining for them pays off when we reach the intrinsic. Additional testing: - [x] Eyeballing Valhalla additions to Unsafe, no other hits - [x] Linux x86_64 server fastdebug, `java/lang/invoke compiler/unsafe` --------- - [x] I confirm that I make this contribution in accordance with the [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). ------------- Commit messages: - A few more paths - Merge branch 'master' into JDK-8395827-unsafe-forceinline - Fix Changes: https://git.openjdk.org/jdk/pull/33564/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=33564&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8395827 Stats: 13 lines in 1 file changed: 13 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/33564.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/33564/head:pull/33564 PR: https://git.openjdk.org/jdk/pull/33564
