C2: Advantage of parse time inlining

Vitaly Davidovich vitalyd at gmail.com
Wed May 13 19:36:33 UTC 2015


Hi guys,

Could someone please explain the advantage, if any, of parse time inlining
in C2? Given that FreqInlineSize is quite large by default, most hot
methods will get inlined anyway (well, ones that can be for other
reasons).  What is the advantage of parse time inlining?

Is it quicker time to peak performance if C1 is reached first?

Does it ensure that a method is inlined whereas it may not be if it's
already compiled into a medium/large method otherwise?

Is parse time inlining not susceptible to profile pollution? I suspect it
is since the interpreter has already profiled the inlinee either way, but
wanted to check.

Anything else I'm not thinking about?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20150513/8cf60f3b/attachment.html>


More information about the hotspot-compiler-dev mailing list