JDK-8336760 : [JVMCI] -XX:+PrintCompilation should also print "hosted" JVMCI compilations
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 17,21,23
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2024-07-18
  • Updated: 2024-07-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8336762 - [JVMCI] Append the jvmci_name to the nmethod name for "hosted" JVMCI compilations
Relates :  
JDK-8149969 - [JVMCI] PrintNMethods is ignored for CompilerToVM.installCode when not called from the broker
Description
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.
Comments
ILW = -XX:+PrintCompilation does not print hosted JVMCI compilations, with JVMCI and -XX:+PrintCompilation, no workaround = MLH = P4
19-07-2024