AtParse denotes that a flag be checked for range/constraint ONLY at parse time, ie. only when the user sets the flag explicitly on command line. It was added to port over the existing runtime flag, but they need to be defined as AfterErgo type, so they get checked during the VM init process.
Therefore we can safely get rid of AtParse and with some small tweaks get the correct behavior.
- relates to
-
JDK-8078556 Runtime: implement ranges (optionally constraints) for those flags that have them missing
-
- Resolved
-
-
JDK-8136421 Integration
-
- Closed
-
-
JDK-8130459 Add additional validation after heap creation
-
- Resolved
-