Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8045235 | 8u25 | Thomas Schatzl | P4 | Resolved | Fixed | b01 |
JDK-8035643 | 8u20 | Thomas Schatzl | P4 | Resolved | Fixed | b04 |
JDK-8053239 | emb-8u26 | Thomas Schatzl | P4 | Resolved | Fixed | b17 |
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.
- 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.
- backported by
-
JDK-8035643 Move G1ParCopyClosure::copy_to_survivor_space into G1ParScanThreadState
-
- Resolved
-
-
JDK-8045235 Move G1ParCopyClosure::copy_to_survivor_space into G1ParScanThreadState
-
- Resolved
-
-
JDK-8053239 Move G1ParCopyClosure::copy_to_survivor_space into G1ParScanThreadState
-
- Resolved
-
- relates to
-
JDK-8035400 Move G1ParScanThreadState into its own files
-
- Resolved
-