Wed, 13 Oct 2010 10:29:31 +0200 6991211: assert failure on sparc: "can not have caller-save register operands at calls"
roland [Wed, 13 Oct 2010 10:29:31 +0200] rev 6777
6991211: assert failure on sparc: "can not have caller-save register operands at calls" Summary: fixes sparc only assert failure following 6972540 Reviewed-by: never
Wed, 13 Oct 2010 13:31:30 -0700 Merge
twisti [Wed, 13 Oct 2010 13:31:30 -0700] rev 6776
Merge
Wed, 13 Oct 2010 01:19:43 -0700 6987555: JSR 292 unboxing to a boolean value fails on big-endian SPARC
twisti [Wed, 13 Oct 2010 01:19:43 -0700] rev 6775
6987555: JSR 292 unboxing to a boolean value fails on big-endian SPARC Reviewed-by: never, jrose
Tue, 12 Oct 2010 23:51:20 -0700 6991512: G1 barriers fail with 64bit C1
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
Tue, 12 Oct 2010 02:21:06 -0700 6991065: missed a review comment in 6829194
twisti [Tue, 12 Oct 2010 02:21:06 -0700] rev 6773
6991065: missed a review comment in 6829194 Reviewed-by: kvn
Mon, 11 Oct 2010 04:18:58 -0700 6829194: JSR 292 needs to support compressed oops
twisti [Mon, 11 Oct 2010 04:18:58 -0700] rev 6772
6829194: JSR 292 needs to support compressed oops Reviewed-by: kvn, jrose
Fri, 08 Oct 2010 02:42:17 -0700 6990549: Zero and Shark fixes after 6978355 and 6953144
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>
Thu, 07 Oct 2010 21:40:55 -0700 6980792: Crash "exception happened outside interpreter, nmethods and vtable stubs (1)"
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
Fri, 08 Oct 2010 09:29:09 -0700 Merge
jcoomes [Fri, 08 Oct 2010 09:29:09 -0700] rev 6769
Merge
Fri, 01 Oct 2010 16:43:05 -0400 6980838: G1: guarantee(false) failed: thread has an unexpected active value in its SATB queue
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
Fri, 01 Oct 2010 21:48:40 -0700 Merge
johnc [Fri, 01 Oct 2010 21:48:40 -0700] rev 6767
Merge
Fri, 01 Oct 2010 18:23:16 -0700 6983311: G1: LoopTest hangs when run with -XX:+ExplicitInvokesConcurrent
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
Fri, 01 Oct 2010 16:12:54 -0700 6794422: Perm gen expansion policy for concurrent collectors
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
Thu, 30 Sep 2010 12:15:13 -0700 6988678: fatal error deadlock handling was unintentionally disabled
jcoomes [Thu, 30 Sep 2010 12:15:13 -0700] rev 6764
6988678: fatal error deadlock handling was unintentionally disabled Reviewed-by: ysr
Wed, 29 Sep 2010 16:17:02 -0700 6692906: CMS: parallel concurrent marking may be prone to hanging or stalling mutators for periods of time
ysr [Wed, 29 Sep 2010 16:17:02 -0700] rev 6763
6692906: CMS: parallel concurrent marking may be prone to hanging or stalling mutators for periods of time Summary: Inserted missing yield(check)s in closures used during the work-stealing phase of parallel concurrent marking, a missing synchronous yield-request in the cms perm gen allocation path, and a terminator-terminator for the offer_termination invocation that monitors the yield status of the concurrent marking task. Elaborated some documentation comments and made some task queue termination loop flags configurable at start-up to aid debugging in the field. Reviewed-by: jmasa, johnc, poonam
Tue, 28 Sep 2010 15:56:15 -0700 6423256: GC stacks should use a better data structure
jcoomes [Tue, 28 Sep 2010 15:56:15 -0700] rev 6762
6423256: GC stacks should use a better data structure 6942771: SEGV in ParScanThreadState::take_from_overflow_stack Reviewed-by: apetrusenko, ysr, pbk
(0) -3000 -1000 -300 -100 -16 +16 +100 +300 +1000 +3000 +10000 +30000 tip