iveresov [Tue, 12 Oct 2010 23:51:20 -0700] rev 6774
6991512: G1 barriers fail with 64bit C1
Summary: Fix compare-and-swap intrinsic problem with G1 post-barriers and issue with branch ranges in G1 stubs on sparc
Reviewed-by: never, kvn
twisti [Tue, 12 Oct 2010 02:21:06 -0700] rev 6773
6991065: missed a review comment in 6829194
Reviewed-by: kvn
twisti [Mon, 11 Oct 2010 04:18:58 -0700] rev 6772
6829194: JSR 292 needs to support compressed oops
Reviewed-by: kvn, jrose
twisti [Fri, 08 Oct 2010 02:42:17 -0700] rev 6771
6990549: Zero and Shark fixes after 6978355 and 6953144
Reviewed-by: twisti
Contributed-by: Gary Benson <gbenson@redhat.com>
never [Thu, 07 Oct 2010 21:40:55 -0700] rev 6770
6980792: Crash "exception happened outside interpreter, nmethods and vtable stubs (1)"
Reviewed-by: kvn
jcoomes [Fri, 08 Oct 2010 09:29:09 -0700] rev 6769
Merge
tonyp [Fri, 01 Oct 2010 16:43:05 -0400] rev 6768
6980838: G1: guarantee(false) failed: thread has an unexpected active value in its SATB queue
Summary: Under certain circumstances a safepoint could happen between a JavaThread object being created and that object being added to the Java threads list. This could cause the active field of that thread's SATB queue to get out-of-sync with respect to the other Java threads. The solution is to activate the SATB queue, when necessary, before adding the thread to the Java threads list, not when the JavaThread object is created. The changeset also includes a small fix to rename the surrogate locker thread from "Surrogate Locker Thread (CMS)" to "Surrogate Locker Thread (Concurrent GC)" since it's also used in G1.
Reviewed-by: iveresov, ysr, johnc, jcoomes
johnc [Fri, 01 Oct 2010 21:48:40 -0700] rev 6767
Merge
johnc [Fri, 01 Oct 2010 18:23:16 -0700] rev 6766
6983311: G1: LoopTest hangs when run with -XX:+ExplicitInvokesConcurrent
Summary: Clear the concurrent marking "in progress" flag while the FullGCCount_lock is held. This avoids a race that can cause back to back System.gc() calls, when ExplicitGCInvokesConcurrent is enabled, to fail to initiate a marking cycle causing the requesting thread to hang.
Reviewed-by: tonyp, ysr
ysr [Fri, 01 Oct 2010 16:12:54 -0700] rev 6765
6794422: Perm gen expansion policy for concurrent collectors
Summary: Concurrent collectors should expand the perm gen without a full STW GC, but possibly by triggering a concurrent collection. Temporary band-aid for G1 where no concurrent collection is kicked off since the perm gen is not collected concurrently.
Reviewed-by: johnc