JDK-8142510 : -XX:+PrintFlagsRanges should print default range value for those flags that have constraint and an implicit range.
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-11-11
  • Updated: 2016-04-21
  • Resolved: 2016-03-30
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
9 b115Fixed
Related Reports
Relates :  
Description
Currently -XX:+PrintFlagsRanges  will print "[ ... ]" for those flags without range.

In order to tell which flags are implemented and which are not, we need a mechanism to tell them apart. Flags with constraints are allowed not to specify explicit range, if default range works, so for such flags (which we do have), we need to modify how  -XX:+PrintFlagsRanges.

We need -XX:+PrintFlagsRanges to substitute default range values "[ MIN, MAX ]" suitable for the flag's type, when printing those flags that have constraints, but no explicit range.
Comments
Adding default ranges to those flags that only have constraint (implicit default range) will allow Dmitry's testing framework to include those flags in testing - increasing priority to P2.
29-01-2016