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

Move G1ParCopyClosure::copy_to_survivor_space into G1ParScanThreadState

    XMLWordPrintable

Details

    • Enhancement
    • Status: Resolved
    • P4
    • Resolution: Fixed
    • 8u20, 9
    • 9
    • hotspot
    • gc
    • b04

    Backports

      Description

        G1ParCopyClosure::copy_to_survivor_space seems wrongly placed in G1ParCopyClosure:

        - the method does not depend on any template parameter, increasing code size
        - it references G1ParScanThreadState a lot

        Due to that, G1ParScanThreadState seems a good target to move the method to.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8035643 Move G1ParCopyClosure::copy_to_survivor_space into G1ParScanThreadState

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8045235 Move G1ParCopyClosure::copy_to_survivor_space into G1ParScanThreadState

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8053239 Move G1ParCopyClosure::copy_to_survivor_space into G1ParScanThreadState

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved
            relates to

            Enhancement - null JDK-8035400 Move G1ParScanThreadState into its own files

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

            Activity

              People

                tschatzl Thomas Schatzl
                tschatzl Thomas Schatzl
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: