Thu, 08 Sep 2011 12:44:04 -0700 7087947: Add regression test for 7068051
kvn [Thu, 08 Sep 2011 12:44:04 -0700] rev 10541
7087947: Add regression test for 7068051 Summary: Add regression test. Reviewed-by: never
Thu, 08 Sep 2011 05:11:31 -0700 7085860: JSR 292: implement CallSite.setTargetNormal and setTargetVolatile as native methods
twisti [Thu, 08 Sep 2011 05:11:31 -0700] rev 10540
7085860: JSR 292: implement CallSite.setTargetNormal and setTargetVolatile as native methods Reviewed-by: jrose, never
Thu, 08 Sep 2011 10:12:25 +0200 7087445: Improve platform independence of JSR292 shared code
bdelsart [Thu, 08 Sep 2011 10:12:25 +0200] rev 10539
7087445: Improve platform independence of JSR292 shared code Summary: changes necessary for some JSR292 ports Reviewed-by: jrose, dholmes
Wed, 07 Sep 2011 12:58:42 -0700 7054211: No loop unrolling done in jdk7b144 for a test update() while loop
kvn [Wed, 07 Sep 2011 12:58:42 -0700] rev 10538
7054211: No loop unrolling done in jdk7b144 for a test update() while loop Summary: restore unrolling code for CaffeineMark. Reviewed-by: never
Tue, 13 Sep 2011 20:28:00 -0700 7090259: Fix hotspot sources to build with old compilers
kvn [Tue, 13 Sep 2011 20:28:00 -0700] rev 10537
7090259: Fix hotspot sources to build with old compilers Summary: Fixed warnings which prevent building VM with old compilers. Reviewed-by: never
Tue, 13 Sep 2011 16:58:35 -0700 7090069: Java launcher hangs in infinite loop on windows when UseNUMA[Interleaving] is specified
iveresov [Tue, 13 Sep 2011 16:58:35 -0700] rev 10536
7090069: Java launcher hangs in infinite loop on windows when UseNUMA[Interleaving] is specified Summary: Fix _numa_used_node_list array size specification Reviewed-by: kvn, johnc, jmasa, ysr
Tue, 13 Sep 2011 12:40:14 -0400 7089625: G1: policy for how many old regions to add to the CSet (when young gen is fixed) is broken
tonyp [Tue, 13 Sep 2011 12:40:14 -0400] rev 10535
7089625: G1: policy for how many old regions to add to the CSet (when young gen is fixed) is broken Summary: When refactoring the code for a previous fix, a condition was not correctly negated which prevents the G1 policy from adding the correct number of old regions to the CSet when the young gen size is fixed. The changeset also fixes a small syntactical issue in g1ErgoVerbose.hpp which is causing compiler warnings. Reviewed-by: brutisso, ysr
Fri, 09 Sep 2011 16:33:13 -0700 Added tag hs22-b05 for changeset 2787676b53cf
jcoomes [Fri, 09 Sep 2011 16:33:13 -0700] rev 10534
Added tag hs22-b05 for changeset 2787676b53cf
Fri, 09 Sep 2011 16:24:12 -0700 7088991: Bump ths hs22 build number to 05
jcoomes [Fri, 09 Sep 2011 16:24:12 -0700] rev 10533
7088991: Bump ths hs22 build number to 05 Reviewed-by: johnc Contributed-by: alejandro.murillo@oracle.com
Fri, 09 Sep 2011 16:17:16 -0700 Merge
jcoomes [Fri, 09 Sep 2011 16:17:16 -0700] rev 10532
Merge
Fri, 09 Sep 2011 14:44:43 +0200 Merge
stefank [Fri, 09 Sep 2011 14:44:43 +0200] rev 10531
Merge
Fri, 09 Sep 2011 05:20:58 -0400 7087717: G1: make the G1PrintRegionLivenessInfo parameter diagnostic
tonyp [Fri, 09 Sep 2011 05:20:58 -0400] rev 10530
7087717: G1: make the G1PrintRegionLivenessInfo parameter diagnostic Reviewed-by: brutisso, ysr
Thu, 08 Sep 2011 16:29:41 +0200 6929868: G1: introduce min / max young gen size bounds
brutisso [Thu, 08 Sep 2011 16:29:41 +0200] rev 10529
6929868: G1: introduce min / max young gen size bounds Summary: Make G1 handle young gen size command line flags more consistently Reviewed-by: tonyp, jwilhelm
Thu, 08 Sep 2011 05:16:49 -0400 7084509: G1: fix inconsistencies and mistakes in the young list target length calculations
tonyp [Thu, 08 Sep 2011 05:16:49 -0400] rev 10528
7084509: G1: fix inconsistencies and mistakes in the young list target length calculations Summary: Fixed inconsistencies and mistakes in the young list target length calculations so that a) the calculated target length is optimal (before, it was not), b) other parameters like max survivor size and max gc locker eden expansion are always consistent with the calculated target length (before, they were not always), and c) the resulting target length was always bound by desired min and max values (before, it was not). Reviewed-by: brutisso, johnc
Wed, 07 Sep 2011 18:58:33 -0700 7086226: UseNUMA fails on old versions of windows
iveresov [Wed, 07 Sep 2011 18:58:33 -0700] rev 10527
7086226: UseNUMA fails on old versions of windows Summary: Return correct answers from os::numa_*() for UMA machines or if NUMA API is not supported Reviewed-by: johnc
Wed, 07 Sep 2011 13:55:42 -0700 4965777: GC changes to support use of discovered field for pending references
ysr [Wed, 07 Sep 2011 13:55:42 -0700] rev 10526
4965777: GC changes to support use of discovered field for pending references Summary: If and when the reference handler thread is able to use the discovered field to link reference objects in its pending list, so will GC. In that case, GC will scan through this field once a reference object has been placed on the pending list, but not scan that field before that stage, as the field is used by the concurrent GC thread to link discovered objects. When ReferenceHandleR thread does not use the discovered field for the purpose of linking the elements in the pending list, as would be the case in older JDKs, the JVM will fall back to the old behaviour of using the next field for that purpose. Reviewed-by: jcoomes, mchung, stefank
(0) -10000 -3000 -1000 -300 -100 -16 +16 +100 +300 +1000 +3000 +10000 +30000 tip