Good news, bad news

[Christian Thalinger]

On May 26, 2011, at 11:24 AM, Jochen Theodorou wrote:
> Am 26.05.2011 11:03, schrieb Christian Thalinger:
> [...]
>> I looked at the inlining tree of fib and everything looks good and is
>> inlined.  There is one invokeExact which is:
>> 
>> @ 43   java.lang.invoke.MethodHandle::invokeExact (42 bytes)   too
>> big
>> 
>> but bumping the MaxInlineSize just shows that it's:
>> 
>> @ 43   java.lang.invoke.MethodHandle::invokeExact (42 bytes)   call
>> site not reached
>> 
>> so it doesn't matter anyway.
> 
> sorry for gutting in here. Is that looking at the inlining tree 
> something normal mortals can also do? I see there some useful 
> information, even without invokedynamic. So is this some debugging code 
> not found in the normal JVM?

Since a couple of HotSpot builds these switches are also available in product builds:  PrintCompilation is a product switch, PrintInlining is a diagnostic switch.

Do it like:

$ java -XX:+PrintCompilation -XX:+UnlockDiagnosticVMOptions -XX:+PrintInlining

-- Christian