Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8134691

CommandLineFlagConstraint::AtParse is not useful and not what we need

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Withdrawn
    • P2
    • 10
    • 9
    • hotspot
    • None

    Description

      JDK-8130459 added CommandLineFlagConstraint::AtParse, but it's not quite what we need.

      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.

      Attachments

        Issue Links

          relates to

          Sub-task - The sub-task of the issue JDK-8078556 Runtime: implement ranges (optionally constraints) for those flags that have them missing

          • P2 - Crashes, loss of data, severe memory leak.
          • Resolved

          Sub-task - The sub-task of the issue JDK-8136421 Integration

          • P1 - Blocks development and/or testing work, production could not run.
          • Closed

          Enhancement - null JDK-8130459 Add additional validation after heap creation

          • P3 - Major loss of function.
          • Resolved

          Activity

            People

              gziemski Gerard Ziemski
              gziemski Gerard Ziemski
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: