RFR: 8359064: Expose reason for marking nmethod non-entrant to JVMCI client

Doug Simon dnsimon at openjdk.org
Tue Jun 10 10:45:47 UTC 2025


On Tue, 10 Jun 2025 07:45:34 GMT, Manuel Hässig <mhaessig at openjdk.org> wrote:

> A naive question: is it possible to somehow share the enum definition in hotspot with the Java side in JVMCI? If all change reasons were enums, they would be much easier to understand.

Not directly but you can have a mirror enum in JVMCI whose ordinal and message could be kept in sync and initialized from native code. As an example, see [jdk.vm.ci.hotspot.HotSpotCompiledCodeStream.Tag](https://github.com/openjdk/jdk/blob/3ff83ec49e561c44dd99508364b8ba068274b63a/src/jdk.internal.vm.ci/share/classes/jdk/vm/ci/hotspot/HotSpotCompiledCodeStream.java#L228).

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

PR Comment: https://git.openjdk.org/jdk/pull/25706#issuecomment-2958619966


More information about the graal-dev mailing list