JDK-8273409 : Receiver type narrowed by CCP does not always trigger post-parse call devirtualization
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 16,17,18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-09-07
  • Updated: 2021-09-28
  • Resolved: 2021-09-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 18
18 b15Fixed
Related Reports
Relates :  
JDK-8257211 - C2: Enable call devirtualization during post-parse phase
Relates :  
JDK-8273496 - Make sure that CCP adds nodes to the IGVN worklist
Description
CCP is often able to narrow the receiver type of a virtual call which in turn should trigger post-parse call devirtualization if the type is exact.
Comments
Changeset: 4866eaa9 Author: Tobias Hartmann <thartmann@openjdk.org> Date: 2021-09-09 13:44:05 +0000 URL: https://git.openjdk.java.net/jdk/commit/4866eaa997b2ee2a47bdcd0d96202f220fb2774d
09-09-2021
ILW = Missed optimization opportunity in C2, rare cases where CCP is able to narrow the receiver type but IGVN does not re-process the call, no workaround = MLH = P4
07-09-2021