On Tue, 13 Jan 2026 11:35:17 GMT, Ruben <[email protected]> wrote: > From an initial experiment, is appears oopmap_index increments about every 8 > instructions on average - though this observation might be specific to a > certain workload. However, if that's the case, current implementation allows > us to encode post-call NOPs metadata for offsets up to 8K. The above approach > would be an improvement in this case: the MOVK/MOVZ-based chunks would allow > us to encode the metadata for offsets up to 16K, while MOVN-based chunks > would improve search for the rest of the cases. > > What do you think about this option?
It sounds rather complicated. It's important that the performance work we do doesn't over complexify the implementation. Whatever we do should be proportionate to the scale of the problem. Post-call NOPs are not a huge deal. Why not use MOVN, and put the data into a stub at the end of the nmethod? ------------- PR Comment: https://git.openjdk.org/jdk/pull/28855#issuecomment-3748496614
