JDK-8281322 : C2: always construct strip mined loop initially (even if strip mining is disabled)
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 19
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2022-02-07
  • Updated: 2022-03-30
  • Resolved: 2022-03-14
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 19
19 b14Fixed
Related Reports
Relates :  
JDK-8283396 - Null pointer dereference in loopnode.cpp:2851
Relates :  
JDK-8276116 - C2: optimize long range checks in int counted loops
Relates :  
JDK-8282045 - When loop strip mining fails, safepoints are removed from loop anyway
Description
Some of the long range check transformations take advantage of the safepoint captured by loop strip mining to extract jvm state.
Comments
Changeset: ea9eeea8 Author: Roland Westrelin <roland@openjdk.org> Date: 2022-03-14 13:59:13 +0000 URL: https://git.openjdk.java.net/jdk/commit/ea9eeea8ffea6ed32a270051c6986f4f059943c0
14-03-2022
ILW = IR test failure, possible performance anomalies; with strip mining off; turn strip mining on = MMM = P3
07-02-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk/pull/7364 Date: 2022-02-07 08:53:41 +0000
07-02-2022