RFR (L): 8046148: JEP 158 Unified JVM Logging
marcus.larsson at oracle.com
Wed Sep 9 08:36:35 UTC 2015
On 2015-09-09 09:48, Chris Newland wrote:
> Hi Marcus,
> Thanks for your answers.
> The nested XML structure of LogCompilation supports the description of
> arbitrarily complicated JIT parsing chains.
> The JIT compiler can log the start of a compilation with an opening XML
> tag and then hand off to the various subsystems (inlining, escape
> analysis, reg alloc etc.) which output child XML nodes and once they
> return the parent tag is closed.
> Do you have any thoughts on how this could be acheived in a non-XML format?
> Kind regards,
I'm not suggesting we go away from the XML format, I just mean that the
current XML-producing code could be modified to use the unified logging
as its output instead of a file. UL could be happily unaware of the fact
that XML is being written to some log file, and there won't be any need
to implement XML support in the UL framework itself.
>>> Once implemented, will the current output formats still be available?
>> Currently there is no specific support for XML output in the unified
>> logging framework. Output can be directed either to stdout, stderr or plain
>> text files. I'm not entirely sure how the migration of the XML logging
>> will be done. Perhaps it will be preceded by an RFE to add better support
>> for XML outputs in the unified logging framework, or it might just be
>> treated as a regular text file.
More information about the hotspot-dev