comparison src/share/vm/gc_implementation/g1/concurrentMark.hpp @ 20293:7df07d855c8e

8048085: Aborting marking just before remark results in useless additional clearing of the next mark bitmap Summary: Skip clearing the next bitmap if we just recently aborted since the full GC already clears this bitmap. Reviewed-by: brutisso
author tschatzl
date Mon, 21 Jul 2014 09:59:46 +0200
parents 2c6ef90f030a
children 6701abbc4441
comparison
equal deleted inserted replaced
20292:5d7a63aee595 20293:7df07d855c8e
734 VerifyOption vo, bool all) PRODUCT_RETURN; 734 VerifyOption vo, bool all) PRODUCT_RETURN;
735 735
736 // Clear the next marking bitmap (will be called concurrently). 736 // Clear the next marking bitmap (will be called concurrently).
737 void clearNextBitmap(); 737 void clearNextBitmap();
738 738
739 // Return whether the next mark bitmap has no marks set.
740 bool nextMarkBitmapIsClear();
741
739 // These two do the work that needs to be done before and after the 742 // These two do the work that needs to be done before and after the
740 // initial root checkpoint. Since this checkpoint can be done at two 743 // initial root checkpoint. Since this checkpoint can be done at two
741 // different points (i.e. an explicit pause or piggy-backed on a 744 // different points (i.e. an explicit pause or piggy-backed on a
742 // young collection), then it's nice to be able to easily share the 745 // young collection), then it's nice to be able to easily share the
743 // pre/post code. It might be the case that we can put everything in 746 // pre/post code. It might be the case that we can put everything in