JDK-8005071 : Incremental inlining for JSR 292
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2012-12-14
  • Updated: 2013-09-04
  • Resolved: 2012-12-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7 JDK 8 Other
7u40Fixed 8Fixed hs24Fixed
Related Reports
Relates :  
JDK-8007144 - Incremental inlining mistakes some call sites for dead ones and doesn't inline them
Relates :  
JDK-8005031 - Some cleanup in c2 to prepare for incremental inlining support
Relates :  
JDK-8005079 - fix LogCompilation for incremental inlining
Relates :  
JDK-8005441 - PhaseStringOpts shouldn't rely on RegionNode::Ideal to eliminate simple diamond Region
Description
Current inlining heuristics are driven by the number of created nodes which is unrelated to the number of live nodes especially after optimizations are applied. C2 should perform inlining in a loop:

while (more_inlining_candidates) {
    apply_optimizations();
    if (number_of_live_nodes > some_number) break;
    inline_more();
}