Hi Chris,
Thank you for your information.
IMHO, LogCompilation is too difficult to migrate to UL.
So I think we should implement basic (?) JIT logs at first.
I uploaded patches for using UL. Please see them.
http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2017-January/025267.html
Thanks,
Yasumasa
On 2017/01/04 17:02, Chris Newland wrote:
Hi Yasumasa-san, all,
I'm also very interested in changes to JIT logging (I'm the author of the
JITWatch tool [1] for visualising JIT-compiler decisions).
JITWatch consumes the LogCompilation (XML) output which contains more
detail (escape analysis etc.) and better contextualisation (inlining
chains etc.) than the tty-based Print* outputs.
I had a brief discussion on how LogCompilation/UL would interact back in
Sep 2015:
http://mail.openjdk.java.net/pipermail/hotspot-dev/2015-September/019788.html
and John Rose left this comment on the JEP
https://bugs.openjdk.java.net/browse/JDK-8046148#comment-13568278 but as
far as I can tell there is no plan to migrate LogCompilation to UL yet.
Kind regards,
Chris
[1] https://github.com/AdoptOpenJDK/jitwatch
On Tue, January 3, 2017 04:08, Yasumasa Suenaga wrote:
Thanks Vladimir,
Definitely not in JDK 9. And I can't say when it could be done or done
at all.
I hope this feature will be implemented ASAP.
Yasumasa
On 2017/01/03 12:00, Vladimir Kozlov wrote:
On 1/2/17 6:33 PM, Yasumasa Suenaga wrote:
Hi all,
Java 9 has JEP 158: Unified JVM Logging.
This JEP describes that existing 'tty->print...' logging should use
unified logging as output. However, C2 compiler does not seem to use
it.
Do you have any plan to use JEP 158 in JIT codes?
Definitely not in JDK 9. And I can't say when it could be done or done
at all.
Regards,
Vladimir
I uploaded Unified JVM logging viewer to GitHub [1].
I want to draw chart(s) or list all JIT'ed methods on it if possible.
(Especially I want to get log from PrintCompilation and
PrintIntrinsics through Unified JVM logging)
Thanks,
Yasumasa
[1] https://github.com/YaSuenag/ulviewer
