-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 26
-
Component/s: hotspot
-
b04
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8373082 | 25.0.3 | Cesar Soares | P4 | Resolved | Fixed | master |
We recently introduced a way to set the reason why an nmethod was being marked as non-entrant, see https://github.com/openjdk/jdk/pull/23980 and https://github.com/openjdk/jdk/pull/25338.
This RFE is to expose in the JVMCI interface the reason why the nmethod was flagged as non-entrant. This will allow JVMCI-based compilers to implement heuristics to handle re-compilations differently based on what happened to earlier versions of a method, see this for instance: https://github.com/oracle/graal/issues/11045
This RFE is to expose in the JVMCI interface the reason why the nmethod was flagged as non-entrant. This will allow JVMCI-based compilers to implement heuristics to handle re-compilations differently based on what happened to earlier versions of a method, see this for instance: https://github.com/oracle/graal/issues/11045
- backported by
-
JDK-8373082 Expose reason for marking nmethod non-entrant to JVMCI client
-
- Resolved
-
- causes
-
JDK-8360168 CodeInvalidationReasonTest.java failed on riscv
-
- Open
-
-
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk25u/1bb9ea9c
-
Commit(master)
openjdk/jdk/2fe12984
-
Review(master)
openjdk/jdk/25706
(1 links to)