RFR: 8350893: Use generated names for hand generated opto runtime blobs

Andrew Dinn adinn at openjdk.org
Mon Mar 3 10:11:39 UTC 2025


On Sat, 1 Mar 2025 19:55:11 GMT, Vladimir Kozlov <kvn at openjdk.org> wrote:

>> The two special case opto runtime blobs that support uncommon trap and exception handling are currently being generated using hard wired blob names determined by port-specific code. They should employ the standard blob names generated from shared declarations in file stubDeclarations.hpp.
>
> @adinn  I am printing assembler code (`-XX:CompileCommand=print,Test::test) on Mac M1 for nmethod and see this with latest JDK:
> 
>   0x000000010ca8c468:   movz            x8, #0x6d00         ;   {runtime_call StubRoutines (finalstubs)}
>   0x000000010ca8c46c:   movk            x8, #0xca0, lsl #16
>   0x000000010ca8c470:   movk            x8, #0x1, lsl #32
>   0x000000010ca8c474:   blr             x8
> 
> 
> before (jdk 23) it was:
> 
> 
>   0x000000011115fe2c:   movz            x8, #0xf340         ;   {runtime_call Stub::nmethod_entry_barrier}
>   0x000000011115fe30:   movk            x8, #0x1106, lsl #16
>   0x000000011115fe34:   movk            x8, #0x1, lsl #32
>   0x000000011115fe38:   blr             x8
> 
> 
> 
> It could be something changed in code generation but **StubRoutines (finalstubs)** is not helpful.

@vnkozlov
> It could be something changed in code generation but StubRoutines (finalstubs) is not helpful.

Agreed. Although, I don't think that relates to this change. I am investigating.

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

PR Comment: https://git.openjdk.org/jdk/pull/23829#issuecomment-2693862546


More information about the hotspot-compiler-dev mailing list