Thu, 08 Apr 2010 12:13:07 -0700 6942223: c1 64 bit fixes
iveresov [Thu, 08 Apr 2010 12:13:07 -0700] rev 5253
6942223: c1 64 bit fixes Summary: This fixes lir_cmp_l2i on x64 and sparc 64bit, and the debug info generation. Reviewed-by: never
Thu, 08 Apr 2010 10:55:40 +0200 6941529: SharedRuntime::raw_exception_handler_for_return_address must reset thread MethodHandle flag
twisti [Thu, 08 Apr 2010 10:55:40 +0200] rev 5252
6941529: SharedRuntime::raw_exception_handler_for_return_address must reset thread MethodHandle flag Summary: During testing a bug was hit when an exception returned to the interpreter and the SP was wrong. Reviewed-by: kvn, never
Wed, 07 Apr 2010 12:39:27 -0700 6940726: Use BIS instruction for allocation prefetch on Sparc
kvn [Wed, 07 Apr 2010 12:39:27 -0700] rev 5251
6940726: Use BIS instruction for allocation prefetch on Sparc Summary: Use BIS instruction for allocation prefetch on Sparc Reviewed-by: twisti
Wed, 07 Apr 2010 10:35:56 -0700 6940733: allocate non static oop fields in super and sub classes together
kvn [Wed, 07 Apr 2010 10:35:56 -0700] rev 5250
6940733: allocate non static oop fields in super and sub classes together Summary: Use FieldsAllocationStyle=2 to allocate non static oop fields in super and sub classes together Reviewed-by: twisti
Wed, 07 Apr 2010 09:37:47 -0700 6940701: Don't align loops in stubs for Niagara sparc
kvn [Wed, 07 Apr 2010 09:37:47 -0700] rev 5249
6940701: Don't align loops in stubs for Niagara sparc Summary: Don't align loops in stubs for Niagara sparc since NOPs are expensive. Reviewed-by: twisti, never
Tue, 06 Apr 2010 15:18:10 -0700 6940677: Use 64 bytes chunk copy for arraycopy on Sparc
kvn [Tue, 06 Apr 2010 15:18:10 -0700] rev 5248
6940677: Use 64 bytes chunk copy for arraycopy on Sparc Summary: For large arrays we should use 64 bytes chunks copy. Reviewed-by: twisti
Tue, 06 Apr 2010 13:39:52 +0200 6940520: CodeCache::scavenge_root_nmethods_do must fix oop relocations
twisti [Tue, 06 Apr 2010 13:39:52 +0200] rev 5247
6940520: CodeCache::scavenge_root_nmethods_do must fix oop relocations Summary: ScavengeRootsInCode can lead to unfixed code-embedded oops. Reviewed-by: kvn, never
Fri, 09 Apr 2010 15:01:49 -0700 Merge
tonyp [Fri, 09 Apr 2010 15:01:49 -0700] rev 5246
Merge
Fri, 09 Apr 2010 13:08:34 -0400 Merge
tonyp [Fri, 09 Apr 2010 13:08:34 -0400] rev 5245
Merge
Wed, 07 Apr 2010 11:43:53 -0700 6940894: G1: assert(new_obj != 0 || ... "should be forwarded") for compaction tests
johnc [Wed, 07 Apr 2010 11:43:53 -0700] rev 5244
6940894: G1: assert(new_obj != 0 || ... "should be forwarded") for compaction tests 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
Tue, 06 Apr 2010 10:59:45 -0400 6909756: G1: guarantee(G1CollectedHeap::heap()->mark_in_progress(),"Precondition.")
tonyp [Tue, 06 Apr 2010 10:59:45 -0400] rev 5243
6909756: G1: guarantee(G1CollectedHeap::heap()->mark_in_progress(),"Precondition.") 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
Mon, 05 Apr 2010 12:19:22 -0400 6940310: G1: MT-unsafe calls to CM::region_stack_push() / CM::region_stack_pop()
tonyp [Mon, 05 Apr 2010 12:19:22 -0400] rev 5242
6940310: G1: MT-unsafe calls to CM::region_stack_push() / CM::region_stack_pop() 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
(0) -3000 -1000 -300 -100 -12 +12 +100 +300 +1000 +3000 +10000 +30000 tip