RFR (S): 8035329: Move G1ParCopyClosure::copy_to_survivor_space into G1ParScanThreadState
jon.masamitsu at oracle.com
Thu Feb 20 03:18:43 UTC 2014
Changes look good.
Would it make sense to move G1ParScanThreadState
into its own file?
On 2/19/2014 7:12 AM, Thomas Schatzl wrote:
> Hi all,
> can I have reviews for the following change that moves
> G1ParCopyClosure::copy_to_survivor_space() into G1ParScanThreadState.
> The previous location of G1ParCopyClosure::copy_to_survivor_space() was
> bad because although it did not depend on any template parameters, it
> was there, resulting in additional duplicate code.
> As for the new destination, G1ParScanThreadState seemed to be the best
> candidate because the method references it a lot (calling a few methods
> from it).
> Also, the next change for JDK-8035330 also depends on _scanner being
> available in G1ParScanThreadState.
> Based on the changes for 8035326 recently posted here.
More information about the hotspot-gc-dev