JDK-8269126 : Rename G1AllowPreventiveGC option to G1UsePreventiveGC
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 17,18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-06-22
  • Updated: 2021-07-15
  • Resolved: 2021-06-29
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 b29Fixed 18Fixed
Related Reports
Relates :  
Description
Rename the G1AllowPreventiveGC diagnostic flag because the "Allow" part is otherwise unused in G1 flags. Use "Use" instead like others.
Comments
Changeset: fc0fd96a Author: Thomas Schatzl <tschatzl@openjdk.org> Date: 2021-06-29 08:34:55 +0000 URL: https://git.openjdk.java.net/jdk17/commit/fc0fd96a5f8faf09264edf4fbc94bf1d8ac7b3a2
29-06-2021

Late enhancement approved by Project Lead.
28-06-2021

Late enhancement request Justification: We would like to rename the flag G1AllowPreventiveGC introduced in JDK-8257774 to G1UsePreventiveGC because it fits better with existing G1 flag naming. Doing it later will cause unnecessary issues when explaining or using this flag for potentially a long time. Risk: Minimal. No backward compatibility issue: this is a diagnostic flag for functionality introduced before JDK 17 FC. No CSR needed because it is a diagnostic flag. This is a search&replace of the old name with the new one. Changes for JDK 17 are available and tested with tier1-5. Integration date estimate: Basically as soon as the exception is granted . The fix for JDK-17 can be reviewed already https://github.com/openjdk/jdk17/pull/132 and has at least internally been reviewed.
24-06-2021