JDK-8037283 : Flags should remember their cmd line state also if modified by ergonomics
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2014-03-13
  • Updated: 2014-10-08
  • Resolved: 2014-10-08
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 9
9Resolved
Related Reports
Blocks :  
JDK-8048093 - Explicitly setting := vs = in the -XX:+PrintFlagsFinal output
Duplicate :  
JDK-8024137 - Flags should be set using the proper macro
Description
Today if a flag is set on the command line and later changed by the ergonomics (FLAG_SET_ERGO) the question FLAG_IS_CMDLINE will reply false. This makes the policy code more difficult to write and maintain since we will have to use a separate variable to remember that the flag was set on the command line.
In some cases we have chosen to update a flag variable without using the proper macro for doing so which will have other consequences (see the related bug about that).

To clean up the initialization code we should change the flag implementation to store its state in a persistent manner so that we can ask if a flag was set on the command line and if it was set by the ergonomics and get truthful answers in all cases.