JDK-8172733 : [JVMCI] add ResolvedJavaMethod.hasNeverInlineDirective
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-01-12
  • Updated: 2017-02-09
  • Resolved: 2017-01-24
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 10 JDK 9
10Fixed 9 b156Fixed
Related Reports
Relates :  
JDK-8173699 - Crash during deoptimization with "assert(result == __null || result->is_oop()) failed: must be oop"
Description
The ResolvedJavaMethod.canBeInlined method captures 2 different constraints on inlining:

1. Whether the method has an explicit directive (e.g., -XX:CompileCommand=dontinline) or a hotspot recognized annotation (e.g., @DontInline).
2. Whether hotspot has marked it not compilable for policy reasons (e.g., failed compilation earlier or has a bytecode breakpoint).

Some JVMCI clients (such as Truffle partial evaluation) are explicitly interested in the former without concern for the latter. To support this oversight, a separate ResolvedJavaMethod.hasNeverInlineDirective method must be added to JMVCI.