Request for Reviews(M): 7092905: C2: Keep track of the number of dead nodes
john.r.rose at oracle.com
Tue Oct 30 13:27:11 PDT 2012
On Oct 30, 2012, at 7:48 AM, Vladimir Ivanov wrote:
> Regarding the currently published version, I think that logging part can
> be improved further.
Those are good suggestions, Vladimir.
> The general question is: do you intentionally print this info into XML
> compiler log? Why don't you use tty instead? All the messages will
> appear on console and will be duplicated in <tty> section in XML log
> anyway and you don't need to bother too much about the format.
Each compiler thread has a separate log section, divided in the <task>s executed by that thread.
The main <tty> log is global, and intended for globally serialized runtime events, such as deoptimizations or GCs or tty->print stuff.
Meanwhile, the compiler (in one more more threads) runs asynchronously to all the Java application threads. So it gets a separate log.
If an interesting event occurs within the time-sequence of a compiler task, it should be logged in that compiler thread's C->log.
When the JVM exits, all the extra compiler logs are catted together onto the end of the main log's output file.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-compiler-dev