C2: Advantage of parse time inlining

John Rose john.r.rose at oracle.com
Thu May 14 18:42:47 UTC 2015


On May 14, 2015, at 11:30 AM, Vladimir Kozlov <vladimir.kozlov at oracle.com> wrote:
> 
> As parser goes and see a call site it check can it inline or not (see opto/bytecodeinfo.cpp, should_inline() and should_not_inline()). There are several conditions which drive inlining and following (most important) flags controls them: MaxTrivialSize, MaxInlineSize, FreqInlineSize, InlineSmallCode, MinInliningThreshold, MaxInlineLevel, InlineFrequencyCount, InlineFrequencyRatio.

There's a bug report to catch complaints about these heuristics:
  https://bugs.openjdk.java.net/browse/JDK-6316156

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20150514/404d3f82/attachment.html>


More information about the hotspot-compiler-dev mailing list