Revisit VM_Version and VM_Version_ext for overlap and consolidation

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 19
    • Affects Version/s: 11
    • Component/s: hotspot
    • b02

      VM_Version_ext has some additional functionality but also not been actively maintained in years. There are probably a lot of cruft about old CPUs that are no longer relevant.

      Investigate possibility of consolidation with VM_Version and take the opportunity to prune the VM_Version_ext code.

      Update: Also the Abstract_VM_Version versus VM_Version split is awkward and results in the ability to "override" methods that should never be overridden. We should be able to generate a single VM_Version class that contains all of the shared and platform specific functions needed - similar to how the os class is created though preferably with a cleaner mechanism like namespaces.

            Assignee:
            Coleen Phillimore
            Reporter:
            Markus Grönlund
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: