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

verify_special_jvm_flags should not cause an assertion failure when version is bumped

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2
    • Resolution: Fixed
    • Affects Version/s: 11
    • Fix Version/s: 11
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b01
    • Verification:
      Verified

      Description

      verify_special_jvm_flags operates only in debug builds and sanity checks the entries in the deprecated/obsoleted/expired/aliased tables. In addition it detects whether we have not yet removed the global variables for flags that are obsolete/expired, and issues a warning. In the latter case though it also returns false and causes the assertion to fail. This make it impossible to bump the JDK version without dealing with every flag en-masse.

      We should issue the warnings but not fail the assert in these cases.

      This need was flagged when we went to JDK 10 (see JDK-8173421) but not actioned.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dholmes David Holmes
              Reporter:
              dholmes David Holmes
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: