JIT compiler information

Ulf Zibis Ulf.Zibis at gmx.de
Wed Jun 23 13:26:44 PDT 2010

Am 23.06.2010 21:33, schrieb Jookalook:
> LogCompilation gives a great overview about which methods get compiled and if
> they were successful and such, but it doesn't tell you why a method doesn't
> pass the test to even be considered for compilation.  Basically, I am trying
> to figure out why some methods in my codebase, that I know are called very
> often, are not being compiled.  Is there some way of seeing information for
> every method that is called in the JVM, not just the ones that pass the
> compilation requirements. That way I would be able to see the specifics on
> why a method is not chosen for compilation.

For compilation I can't tell you, but for inlining a special case can occur:

At the time, where method a, which calls method b, becomes compiled, the 
threshold for inlining b might not have been reached.
If later the threshold for inlining b theoretically will be reached, 
there is kinda bad chance to become inlined then. But in extrem cases 
there is some chance to become inlined later by result of the HotSpot 
This case may be missed by the HotSpot logger ???

If I'm wrong, someone may correct me.


> Remi Forax wrote:
>> Le 21/06/2010 23:12, Viktor Jucas a écrit :
>> why:
>> http://wikis.sun.com/display/HotSpotInternals/LogCompilation+overview
>> how:
>> http://wikis.sun.com/display/HotSpotInternals/PrintAssembly
>> cheers,
>> Rémi

More information about the hotspot-compiler-dev mailing list