hg: jdk7/hotspot-comp/hotspot: 11 new changesets
john.r.rose at oracle.com
john.r.rose at oracle.com
Tue Apr 13 17:05:46 PDT 2010
Date: 2010-03-31 16:51 -0700
6938627: Make temporary directory use property java.io.tmpdir when specified
Summary: Get java.io.tmpdir property in os::get_temp_directory() and call this instead of harcoding "/tmp". Don't assume trailing file_separator either.
Reviewed-by: dholmes, kamg
Date: 2010-04-02 17:04 -0700
Date: 2010-04-07 12:28 -0400
Date: 2010-03-30 15:36 -0400
6937160: G1: should observe GCTimeRatio
Summary: Remove the G1GCPercent parameter, that specifies the desired GC overhead percentage in G1, and observe the GCTimeRatio parameter instead.
Reviewed-by: jmasa, johnc
Date: 2010-04-02 12:10 -0400
6677708: G1: re-enable parallel RSet updating and scanning
Summary: Enable parallel RSet updating and scanning.
Reviewed-by: iveresov, jmasa
Date: 2010-04-05 12:19 -0400
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
Date: 2010-04-06 10:59 -0400
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
Date: 2010-04-07 11:43 -0700
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
Date: 2010-04-09 13:08 -0400
Date: 2010-04-09 15:01 -0700
Date: 2010-04-13 13:01 -0700
More information about the hotspot-compiler-dev