Summary: ensure_parsability() must be called even if GC_locker prevents GC.
Reviewed-by: ysr, chrisphi

Summary: The outgoing region map is not maintained properly and it's causing an assert failure. Given that we don't actually use it, I'm removing it. I'm piggy-backing a small change on this which removes a message that it's printed before a Full GC when DisableExplicitGC is set.
Reviewed-by: apetrusenko, ysr

Summary: The expression that calculates the live bytes for a heap region can overflow for a suitably large humongous region/object. Cache the object size in a suitably sized local variable so that the expression is converted to a wider type.
Reviewed-by: tonyp, jmasa, iveresov, apetrusenko

Summary: Various fixes to the G1 debugging output.
Reviewed-by: johnc, iveresov

Summary: Ensure a full GC that clears SoftReferences before throwing an out-of-memory
Reviewed-by: ysr, jcoomes

Summary: Humongous regions may contain multiple objects as a result of being retained as to-space from a previous GC and then re-used as to-space after being tagged as humongous. These changes include a check that causes retained to-space regions that are now tagged as humongous to be disregarded and a new to-space region allocated.
Reviewed-by: tonyp, iveresov

Summary: Make sure that two marking cycles do not overlap, i.e., a new one can only start after the concurrent marking thread finishes all its work. In the fix I piggy-back a couple of minor extra fixes: some general code reformatting for consistency (only around the code I modified), the removal of a field (G1CollectorPolicy::_should_initiate_conc_mark) which doesn't seem to be used at all (it's only set but never read), as well as moving the "is GC locker active" test earlier into the G1 pause / Full GC and using a more appropriate method for it.
Reviewed-by: johnc, jmasa, jcoomes, ysr

Summary: Calling the methods region_stack_push() and region_stack_pop() concurrent is not MT-safe. The assumption is that we will only call region_stack_push() during a GC pause and region_stack_pop() during marking. Unfortunately, we also call region_stack_push() during marking which seems to be introducing subtle marking failures. This change introduces lock-based methods for pushing / popping to be called during marking.
Reviewed-by: iveresov, johnc

Summary: Fix typo.
Reviewed-by: never

Summary: Enable parallel RSet updating and scanning.
Reviewed-by: iveresov, jmasa

Reviewed-by: kvn

Reviewed-by: never
Contributed-by: ed@camswl.com

Summary: The changes of 6934494 have broken the Zero build.
Reviewed-by: twisti
Contributed-by: NGary Benson <gbenson@redhat.com>

Summary: Remove the G1GCPercent parameter, that specifies the desired GC overhead percentage in G1, and observe the GCTimeRatio parameter instead.
Reviewed-by: jmasa, johnc

Summary: When Zero is running with Shark enabled threads can be left with their _do_not_unlock_if_synchronized flag incorrectly set.
Reviewed-by: twisti
Contributed-by: NGary Benson <gbenson@redhat.com>

Summary: Remove assert to decouple JDK and HotSpot additions of known types.
Reviewed-by: mchung

Reviewed-by: twisti

Summary: Add close to returns (fix for 6929067 also contributed by aph)
Reviewed-by: aph, dcubed, andrew, acorn
Contributed-by: aph@redhat.com, andreas.kohn@fredhopper.com

Summary: process one item at a time from the objarray stack/queue
Reviewed-by: apetrusenko, tonyp

Summary: Newly-created threads always had the active field of their SATB queue initialized to false, even if they were created during marking. As a result, updates from threads created during a marking cycle were never enqueued and never processed. The fix includes remaining a method from active() to is_active() for readability and naming consistency.
Reviewed-by: ysr, johnc

Summary: Some code cleanups found during the JSR 292 SPARC port.
Reviewed-by: kvn, never

Summary: If CM task was aborted while scanning the last object of the specified region and the size of that object is equal to bitmap's granularity then the next offset would be equal or over the region limit which is exactly what the assertion states.
Reviewed-by: ysr, tonyp, jmasa

Reviewed-by: kvn

Summary: Added missing counter decrement when substring search restarted.
Reviewed-by: twisti

Summary: Adding probes related to thread scheduling and class initialization
Reviewed-by: kamg, never

Summary: The logic for x86 C1 to save the SP over MH calls is pretty straight forward but SPARC handles that differently.
Reviewed-by: never, jrose

Summary: Add missing guard.
Reviewed-by: never

Summary: Passing a null pointer to an InvokeDynamic function call should lead to a NullPointerException.
Reviewed-by: kvn, never

Summary: Restore code deleted in 6626217
Reviewed-by: asaha, kevinw

Summary: Use -XX:+TraceSafepointCleanupTime to print out the details of each clean up tasks.
Reviewed-by: dholmes, ysr

Summary: Add code to unmap stack guard area when thread is detached.
Reviewed-by: coleenp, kamg

Summary: A TLAB became large enough to be considered a humongous object allowing multiple objects to be allocated in a humongous region, which violates a basic assumption about humongous regions. The changes ensure that TLABs cannot be regarded as humongous.
Reviewed-by: iveresov, tonyp

Summary: The fix for 6927165 increased the number of shadow pages for 32-bit platforms and this causes a problem on systems with 64kb pages.
Reviewed-by: twisti
Contributed-by: NGary Benson <gbenson@redhat.com>

Summary: Improve the usability of safepoint statistics data. See bug evaluation for more details.
Reviewed-by: ysr, dholmes

Summary: store jsr ret bci as intptr constant in c1 debug info
Reviewed-by: never

Summary: This implements JSR 292 support for C1 x86.
Reviewed-by: never, jrose, kvn

Summary: A modified MethodHandlesTest revealed two bugs on x86_64.
Reviewed-by: never, jrose

Summary: Use an explicit stack for object arrays and process them in chunks.
Reviewed-by: iveresov, apetrusenko

Summary: Calculation of the slicing of survivor spaces for MT was incorrect.
Reviewed-by: ysr

Summary: Move creating stack guard pages in jni attach thread before potential java call rather than after. Also cleanup stack guard pages when jni attach fails
Reviewed-by: never, dholmes