bae [Mon, 17 Oct 2011 15:20:51 +0400] rev 10778
6997116: The case automatically failed due to java.lang.ClassCastException.
Reviewed-by: jgodinez, prr
katleman [Thu, 27 Oct 2011 13:54:42 -0700] rev 10777
Added tag jdk8-b11 for changeset 7116fbba4c13
duke [Wed, 05 Jul 2017 17:54:00 +0200] rev 10776
Merge
jcoomes [Fri, 28 Oct 2011 15:41:29 -0700] rev 10775
Added tag hs23-b04 for changeset 721977078d6e
jcoomes [Fri, 28 Oct 2011 15:36:16 -0700] rev 10774
Merge
tonyp [Fri, 28 Oct 2011 12:49:16 -0400] rev 10773
Merge
brutisso [Wed, 26 Oct 2011 08:44:53 +0200] rev 10772
7102191: G1: assert(_min_desired_young_length <= initial_region_num) failed: Initial young gen size too small
Summary: initial_region_num actually not needed.
Reviewed-by: tonyp, johnc
ysr [Tue, 25 Oct 2011 20:15:41 -0700] rev 10771
7099817: CMS: +FLSVerifyLists +FLSVerifyIndexTable asserts: odd slot non-empty, chunk not on free list
Summary: Suitably weaken asserts that were in each case a tad too strong; fix up some loose uses of parameters in code related to size-indexed free list table.
Reviewed-by: jmasa, brutisso, stefank
johnc [Sun, 23 Oct 2011 23:06:06 -0700] rev 10770
7096030: G1: PrintGCDetails enhancements
7102445: G1: Unnecessary Resource allocations during RSet scanning
Summary: Add a new per-worker thread line in the PrintGCDetails output. GC Worker Other is the difference between the elapsed time for the parallel phase of the evacuation pause and the sum of the times of the sub-phases (external root scanning, mark stack scanning, RSet updating, RSet scanning, object copying, and termination) for that worker. During RSet scanning, stack allocate DirtyCardToOopClosure objects; allocating these in a resource area was causing abnormally high GC Worker Other times while the worker thread freed ResourceArea chunks.
Reviewed-by: tonyp, jwilhelm, brutisso
johnc [Thu, 20 Oct 2011 12:06:20 -0700] rev 10769
7099824: G1: we should take the pending list lock before doing the remark pause
Summary: Acquire the pending list lock in the prologue method of G1's concurrent VM_Operation and release the lock in the epilogue() method. The locking/unlocking order of the pending list lock and the Heap_lock should match that in the prologue and epilogue methods of VM_GC_Operation.
Reviewed-by: tonyp, ysr