RFR: Experiment with storing target method for static and opt-virtual callsites in reloc info
Vladimir Ivanov
vlivanov at openjdk.org
Wed Dec 10 22:56:18 UTC 2025
On Wed, 10 Dec 2025 22:35:59 GMT, Ashutosh Mehra <asmehra at openjdk.org> wrote:
>> src/hotspot/share/runtime/sharedRuntime.cpp line 1528:
>>
>>> 1526:
>>> 1527: if (UseNewCode2) {
>>> 1528: bool is_mhi;
>>
>> I believe disabling inlining through MH linkers when generating archived code should simplify things. Then, there should be no attached methods for MH linkers in archived code and vise-versa.
>
> Are you suggesting disable inlining through MH linkers for both aot and jit code, or only for the aot code? If we do only for the aot code, it wouldn't help unless we decided to do this optimization only for the aot code. As it stands, it benefits bot jit and aot code.
I'd assume it is less important for JITed code. The problem is so acute for AOTed code because it's so cheap to retrieve and install it, so we have plenty of AOT code published in a short period during application startup.
-------------
PR Review Comment: https://git.openjdk.org/leyden/pull/106#discussion_r2608489290
More information about the leyden-dev
mailing list