JDK-8007988 : PrintInlining output is inconsistent with incremental inlining
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-02-12
  • Updated: 2025-02-07
  • Resolved: 2014-04-09
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 9
9 b10Fixed
Related Reports
Relates :  
JDK-8235998 - [C2] Memory leaks during tracing after "8224193: stringStream should not use Resource Area".
Description
The PrintInlining output always reports a call site candidate for incremental inlining as "inline (hot)" whether the call site is actually inlined or not which results in duplicate lines most of the time (one "inline (hot)" and one "live nodes > LiveNodeCountInliningCutoff").
Comments
URL: http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/33cc0d9740a8 User: lana Date: 2014-04-23 16:11:22 +0000
23-04-2014
URL: http://hg.openjdk.java.net/jdk9/hs-comp/hotspot/rev/33cc0d9740a8 User: roland Date: 2014-04-09 08:51:35 +0000
09-04-2014