ysr [Wed, 18 Aug 2010 11:39:21 -0700] rev 6262
6977970: CMS: concurrentMarkSweepGeneration.cpp:7947 assert(addr <= _limit) failed: sweep invariant
Summary: Allow for the possibility (when the heap is expanding) that the sweep might skip over and past, rather than necessarily step on, the sweep limit determined at the beginning of a concurrent marking cycle.
Reviewed-by: jmasa, tonyp
tonyp [Tue, 17 Aug 2010 14:40:00 -0400] rev 6261
6975964: G1: print out a more descriptive message for evacuation failure when +PrintGCDetails is set
Summary: we're renaming "evacuation failure" to "to-space overflow". I'm also piggy-backing a small additional change which removes the "Mark closure took..." output.
Reviewed-by: ysr, johnc
tonyp [Tue, 17 Aug 2010 14:40:00 -0400] rev 6260
6974928: G1: sometimes humongous objects are allocated in young regions
Summary: as the title says, sometimes we are allocating humongous objects in young regions and we shouldn't.
Reviewed-by: ysr, johnc
tonyp [Tue, 17 Aug 2010 14:40:00 -0400] rev 6259
6959014: G1: assert(minimum_desired_capacity <= maximum_desired_capacity) failed: sanity check
Summary: There are a few issues in the code that calculates whether to resize the heap and by how much: a) some calculations can overflow 32-bit size_t's, b) min_desired_capacity is not bounded by the max heap size, and c) the assrt that fires is in the wrong place. The fix also includes some tidying up of the related verbose code.
Reviewed-by: ysr, jmasa
ysr [Mon, 16 Aug 2010 15:58:42 -0700] rev 6258
6948538: CMS: BOT walkers can fall into object allocation and initialization cracks
Summary: GC workers now recognize an intermediate transient state of blocks which are allocated but have not yet completed initialization. blk_start() calls do not attempt to determine the size of a block in the transient state, rather waiting for the block to become initialized so that it is safe to query its size. Audited and ensured the order of initialization of object fields (klass, free bit and size) to respect block state transition protocol. Also included some new assertion checking code enabled in debug mode.
Reviewed-by: chrisphi, johnc, poonam
asaha [Tue, 17 Aug 2010 22:52:50 -0700] rev 6257
6977952: Test: Sync missing tests from hs16.3 to hs17.x
Reviewed-by: wrockett
trims [Wed, 18 Aug 2010 16:11:21 -0700] rev 6256
Merge
johnc [Sat, 14 Aug 2010 00:47:52 -0700] rev 6255
Merge
jcoomes [Wed, 11 Aug 2010 13:12:28 -0700] rev 6254
6976378: ParNew: stats are printed unconditionally in debug builds
Reviewed-by: tonyp
ysr [Tue, 10 Aug 2010 14:53:35 -0700] rev 6253
6973570: OrderAccess::storestore() scales poorly on multi-socket x64 and sparc: cache-line ping-ponging
Summary: volatile store to static variable removed in favour of a volatile store to stack to avoid excessive cache coherency traffic; verified that the volatile store is not elided by any of our current compilers.
Reviewed-by: dholmes, dice, jcoomes, kvn
jcoomes [Mon, 09 Aug 2010 18:03:50 -0700] rev 6252
6970376: ParNew: shared TaskQueue statistics
Reviewed-by: ysr
jcoomes [Mon, 09 Aug 2010 05:41:05 -0700] rev 6251
6966222: G1: simplify TaskQueue overflow handling
Reviewed-by: tonyp, ysr
johnc [Fri, 06 Aug 2010 10:17:21 -0700] rev 6250
6930581: G1: assert(ParallelGCThreads > 1 || n_yielded() == _hrrs->occupied(),"Should have yielded all the ..
Summary: During RSet updating, when ParallelGCThreads is zero, references that point into the collection set are added directly the referenced region's RSet. This can cause the sparse table in the RSet to expand. RSet scanning and the "occupied" routine will then operate on different instances of the sparse table causing the assert to trip. This may also cause some cards added post expansion to be missed during RSet scanning. When ParallelGCThreads is non-zero such references are recorded on the "references to be scanned" queue and the card containing the reference is recorded in a dirty card queue for use in the event of an evacuation failure. Employ the parallel code in the serial case to avoid expanding the RSets of regions in the collection set.
Reviewed-by: iveresov, ysr, tonyp
tonyp [Wed, 04 Aug 2010 13:03:23 -0400] rev 6249
6963209: G1: remove the concept of abandoned pauses
Summary: As part of 6944166 we disabled the concept of abandoned pauses (i.e., if the collection set is empty, we would still try to do a pause even if it is to update the RSets and scan the roots). This changeset removes the code and structures associated with abandoned pauses.
Reviewed-by: iveresov, johnc