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.
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.
- blocks
-
JDK-8048093 Explicitly setting := vs = in the -XX:+PrintFlagsFinal output
-
- Resolved
-
- duplicates
-
JDK-8024137 Flags should be set using the proper macro
-
- Resolved
-