JDK-8271118 : C2: StressGCM should have higher priority than frequency-based policy
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 17,18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-07-22
  • Updated: 2024-08-08
  • Resolved: 2021-07-28
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 17 JDK 18
17.0.11-oracleFixed 18 b08Fixed
Related Reports
Duplicate :  
JDK-8257146 - C2: extend the scope of StressGCM
Description
Create on behalf of Kuai Wei
-----

I think StressGCM should have higher priority than frequency-based policy, otherwise StressGCM has no chance to choose because the frequency-based policy would choose block first if appropriately.
Comments
[jdk17u-fix-request] Approval Request from Aleksey Shipilëv Clean backport to greatly extend the scope of StressGCM. This would allow better compiler testing, including test backports (which rely on StressGCM with given seed to reproduce sometimes), and jcstress runs (which automatically opts in to StressGCM). More details in PR.
11-12-2023
A pull request was submitted for review. URL: https://git.openjdk.org/jdk17u-dev/pull/2038 Date: 2023-12-11 15:15:47 +0000
11-12-2023
Changeset: ed1cb240 Author: Yi Yang <yyang@openjdk.org> Date: 2021-07-28 02:17:30 +0000 URL: https://git.openjdk.java.net/jdk/commit/ed1cb24027f48ec8e243c26e1847561fa902d91f
28-07-2021