tonyp [Tue, 24 Jan 2012 17:08:58 -0500] rev 11582
7132398: G1: java.lang.IllegalArgumentException: Invalid threshold: 9223372036854775807 > max (1073741824)
Summary: Was not passing the right old pool max to the memory pool constructor in the fix for 7078465.
Reviewed-by: brutisso, johnc
brutisso [Mon, 23 Jan 2012 20:36:16 +0100] rev 11581
7132311: G1: assert((s == klass->oop_size(this)) || (Universe::heap()->is_gc_active() && ((is_typeArray()...
Summary: Move the check for when to call collect() to before we do a humongous object allocation
Reviewed-by: stefank, tonyp
brutisso [Fri, 20 Jan 2012 18:01:32 +0100] rev 11580
7131791: G1: Asserts in nightly testing due to 6976060
Summary: Create a handle and fake an object to make sure that we don't loose the memory we just allocated
Reviewed-by: tonyp, stefank
tonyp [Thu, 19 Jan 2012 09:13:58 -0500] rev 11579
7078465: G1: Don't use the undefined value (-1) for the G1 old memory pool max size
Reviewed-by: johnc, brutisso
johnc [Tue, 17 Jan 2012 10:21:43 -0800] rev 11578
7129271: G1: Interference from multiple threads in PrintGC/PrintGCDetails output
Summary: During an initial mark pause, signal the Concurrent Mark thread after the pause output from PrintGC/PrintGCDetails is complete.
Reviewed-by: tonyp, brutisso
tonyp [Wed, 18 Jan 2012 10:30:12 -0500] rev 11577
7097586: G1: improve the per-space output when using jmap -heap
Summary: Extend the jmap -heap output for G1 to include some more G1-specific information.
Reviewed-by: brutisso, johnc, poonam
brutisso [Mon, 16 Jan 2012 22:10:05 +0100] rev 11576
6976060: G1: humongous object allocations should initiate marking cycles when necessary
Reviewed-by: tonyp, johnc
brutisso [Mon, 16 Jan 2012 11:21:21 +0100] rev 11575
7130334: G1: Change comments and error messages that refer to CMS in g1/concurrentMark.cpp/hpp
Summary: Removed references to CMS in the concurrentMark.cpp/hpp files.
Reviewed-by: tonyp, jmasa, johnc
johnc [Fri, 13 Jan 2012 13:27:48 -0800] rev 11574
7121547: G1: High number mispredicted branches while iterating over the marking bitmap
Summary: There is a high number of mispredicted branches associated with calling BitMap::iteratate() from within CMBitMapRO::iterate(). Implement a version of CMBitMapRO::iterate() directly using inline-able routines.
Reviewed-by: tonyp, iveresov
jrose [Thu, 26 Jan 2012 19:39:08 -0800] rev 11573
Merge