RFR: 8316694: Implement relocation of nmethod within CodeCache [v3]

Chad Rakoczy duke at openjdk.org
Fri May 30 22:55:05 UTC 2025


On Fri, 30 May 2025 01:17:49 GMT, Vladimir Kozlov <kvn at openjdk.org> wrote:

>> I still have that concern for **mutable**  data which includes relocations which accessed frequently.
>> 
>> I don't think accessing **immutable** is performance critical. They mostly accessed during deoptimization and from JVMTI.
>
> Actually even **mutable** is not critical since we did not include oops data section (we keep it with nmethod). It currently contains relocations, metadata (klass*, method*) and JVMCI data. We can experiment in separate RFE if we can use separate class for it too.

I have created a RFE to move the immutable data from the nmethod to a separate class. [JDK-8358213](https://bugs.openjdk.org/browse/JDK-8358213)

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

PR Review Comment: https://git.openjdk.org/jdk/pull/23573#discussion_r2116837278


More information about the hotspot-compiler-dev mailing list