Status of LogCompilation in latest JDK9 builds?
Chris Newland
cnewland at chrisnewland.com
Fri Dec 11 11:45:38 UTC 2015
Hi,
I've noticed in the last few JDK9 beta builds from java.net and in the tip
of http://hg.openjdk.java.net/jdk9/dev/ that LogCompilation output is
mostly missing when using -XX:+UnlockDiagnosticVMOptions and
-XX:+LogCompilation
<task_queued> and <nmethod> tags are present but <task> tags contain no
children apart from <task_done>:
<task compile_id='150' method='java.lang.StringLatin1 toUpperCase
(Ljava/lang/String;[BLjava/util/Locale;)Ljava/lang/String;' bytes='180'
count='1890' backedge_count='5014' iicount='1890' stamp='5.047'>
<task_done success='1' nmsize='1880' count='5000' backedge_count='5003'
inlined_bytes='506' stamp='5.061'/>
</task>
<task compile_id='154'
method='org.adoptopenjdk.jitwatch.demo.MakeHotSpotLog toUpper
([Ljava/lang/String;[Ljava/lang/String;I)V' bytes='27' count='1014'
backedge_count='5121' iicount='1014' stamp='5.062'>
<task_done success='1' nmsize='648' count='5000' backedge_count='5009'
inlined_bytes='60' stamp='5.067'/>
</task>
Adding -Xlog:all=trace doesn't help. Output is missing for C1 and C2
compilations.
Is this expected behaviour at this point in the development of unified
logging?
The <task> tags used to contain all of the useful information used by
JITWatch to visualise the JIT behaviour.
Thanks,
Chris
More information about the hotspot-runtime-dev
mailing list