RFR: 8352415: x86: Tighten up template interpreter method entry code

[Andrew Dinn]

On Wed, 19 Mar 2025 13:44:40 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

> Interpreter performance is the still important for faster startup, since it would carry application until compilers kick in. After looking at Leyden scenarios in Xint mode, I believe incremental improvements are possible in template interpreter to make it faster.
> 
> One of those improvements is tightening up method entry code. Profiling shows the hottest path in the whole ordeal for non-native methods is resolving the Java mirror to store the GC root for currently executing Method*. It involves 4-5 chained memory accesses, which incurs significant latency.
> 
> We can massage the code to reuse some memory accesses and also spread them out to allow more latency-hiding hardware mechanisms to kick in.
> 
> Additional testing:
>  - [x] Ad-hoc `-Xint` benchmarks
>  - [ ] Linux x86_64 server fastdebug, `all`

src/hotspot/cpu/x86/templateInterpreterGenerator_x86.cpp line 656:

> 654:   // Resolve ConstMethod* -> ConstantPool*.
> 655:   // Get codebase, while we still have ConstMethod*.
> 656:   // Save ConstantPool* in rax for later use.

Oh nice!

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

PR Review Comment: https://git.openjdk.org/jdk/pull/24114#discussion_r2003577225