-
Bug
-
Resolution: Fixed
-
P4
-
17, 21, 23
-
b08
Currently, `-XX:+PrintCompilation` does not print "hosted" JVMCI compilations (i.e. JVMCI compilations not triggered by the `CompilerBroker` but e.g. by the Truffle framework). On the other hand, if such an nmethod which results from a "hosted" compilation gets deoptimized, it will be printed by `-XX:+PrintCompilation` (with a compilation ID that doesn't appear anywhere before in the compilation log.
This behavior is confusing and should be fixed. Any nmethod installed in the code cache should be logged by `-XX:+PrintCompilation` no matter if its compilation was triggered by the `CompileBroker` or from another library through JVMCI.
This behavior is confusing and should be fixed. Any nmethod installed in the code cache should be logged by `-XX:+PrintCompilation` no matter if its compilation was triggered by the `CompileBroker` or from another library through JVMCI.
- is cloned by
-
JDK-8348621 [JVMCI] Consider enabling -XX:+PrintCompilation2 and/or -XX:+CITime for "hosted" JVMCI compilations
-
- Open
-
- relates to
-
JDK-8336762 [JVMCI] Append the jvmci_name to the nmethod name for "hosted" JVMCI compilations
-
- Open
-
-
JDK-8149969 [JVMCI] PrintNMethods is ignored for CompilerToVM.installCode when not called from the broker
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/c3c38887
-
Review(master) openjdk/jdk/23278