This is being taken up on hotspot-runtime-dev, but I wanted to make a
couple of responses to Alan ...
On 6/06/2012 12:43 AM, Alan Bateman wrote:
I would suggest moving the thread to hotspot-dev or hotspot-runtime-dev.
On attempting to use -XX:MaxDirectMemorySize=5g on a 32-bit system then
idea
hs23.2-b04 has been integrated into jdk7u6-b13.
http://hg.openjdk.java.net/jdk7u/jdk7u/rev/9b9a6d318e8a
http://hg.openjdk.java.net/jdk7u/jdk7u/corba/rev/76bee3576f61
http://hg.openjdk.java.net/jdk7u/jdk7u/hotspot/rev/28746e6d615f
http://hg.openjdk.java.net/jdk7u/jdk7u/jaxp/rev/15b71daf5e69
http:/
Changeset: d8fb2e80e074
Author:amurillo
Date: 2012-05-25 13:53 -0700
URL: http://hg.openjdk.java.net/jdk7u/jdk7u/hotspot/rev/d8fb2e80e074
7171852: new hotspot build - hs23.2-b04
Reviewed-by: jcoomes
! make/hotspot_version
Changeset: 7d4e6dabc6bf
Author:dcubed
Date: 2012-0
Changeset: d8fb2e80e074
Author:amurillo
Date: 2012-05-25 13:53 -0700
URL: http://hg.openjdk.java.net/jdk7u/jdk7u-dev/hotspot/rev/d8fb2e80e074
7171852: new hotspot build - hs23.2-b04
Reviewed-by: jcoomes
! make/hotspot_version
Changeset: 7d4e6dabc6bf
Author:dcubed
Date: 20
Changeset: 36f64ab3c9ca
Author:katleman
Date: 2012-05-31 14:06 -0700
URL: http://hg.openjdk.java.net/jdk7u/jdk7u-dev/hotspot/rev/36f64ab3c9ca
Added tag jdk7u6-b12 for changeset f08a3a0e60c3
! .hgtags
As Alan suggested I've created a new thread on hotspot-runtime-dev to discuss
the command line parsing issues.
On Jun 5, 2012, at 10:43 AM, Alan Bateman wrote:
> On 05/06/2012 15:29, Chris Dennis wrote:
>> Alan,
>>
>> The 5g issue is kind of complicated. The current behavior of 32bit JVMs as
On 05/06/2012 15:29, Chris Dennis wrote:
Alan,
The 5g issue is kind of complicated. The current behavior of 32bit JVMs as I
understand it is that the 5g will get narrowed down to a 32bit value by the
printf used to propagate the value across from the launcher and in to the
system properties
Alan,
The 5g issue is kind of complicated. The current behavior of 32bit JVMs as I
understand it is that the 5g will get narrowed down to a 32bit value by the
printf used to propagate the value across from the launcher and in to the
system properties of the spawned JVM. Consider the result of
David,
My feeling on this is that the Hotspot changes should go through
hotspot-runtime-dev, and that since they represent a fix to a recent regression
(in 1.7.0_04) they should probably go now without waiting for the test changes
in the jdk project. I'll start a new thread on hotspot-runtime-
On 04/06/2012 14:38, Chris Dennis wrote:
:
The patch to increase test coverage to cover this issue is against the jdk
sources, however the issue here is more complicated. While modifying the
LimitDirectMemory.sh jtreg test to cover this issue I've run in to some
problems with the test - the
10 matches
Mail list logo
