Hotspot profiles by bytecode; as a result, some shared methods become polluted and suffer in type profiling, as described in depth in [this essay](https://cr.openjdk.org/~jrose/jvm/equals-profile.html) by John Rose. The record methods generated by `ObjectMethods::bootstrap` just proved itself another victim in this RFE.
To bypass this issue, I naively generated distinct bytecode to allow distinct profiles for now. If hotspot adds any kind of split profiles exposed via internal APIs, we can migrate to such split profile and throw away these extra copies of bytecode. In particular, in a method handle tree, each leaf method handle seems not separately profiled - for example, all DMH to Object.hashCode share the same profile regardless of their position in a MH tree, making MH trees less useful than explicitly rolled bytecode, unfortunately. The attached benchmark should be a good demonstration of the effect of type profiling. ------------- Commit messages: - Merge branch 'master' of https://github.com/openjdk/jdk into fix/object-methods-profile - Improve bench, add comment - Fix profiling issue with record shared code - Unsuccessful attempt to fix record regression Changes: https://git.openjdk.org/jdk/pull/27533/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=27533&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8366424 Stats: 348 lines in 2 files changed: 298 ins; 18 del; 32 mod Patch: https://git.openjdk.org/jdk/pull/27533.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/27533/head:pull/27533 PR: https://git.openjdk.org/jdk/pull/27533
