> Hi all,
>
> vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java fails on our
> many-core machines due to `-XX:MaxRAMPercentage=0`.
> This is because `MaxRAMPercentage` will be always 0 if JTREG_JOBS > 25 [1].
>
> It can be reproduced by: `make test
>
On Mon, 17 May 2021 13:24:16 GMT, Jie Fu wrote:
> Hi all,
>
> vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java fails on our
> many-core machines due to `-XX:MaxRAMPercentage=0`.
> This is because `MaxRAMPercentage` will be always 0 if JTREG_JOBS > 25 [1].
>
> It can be reproduced
On Mon, 17 May 2021 17:17:00 GMT, Aleksey Shipilev wrote:
>> Hi all,
>>
>> vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java fails on our
>> many-core machines due to `-XX:MaxRAMPercentage=0`.
>> This is because `MaxRAMPercentage` will be always 0 if JTREG_JOBS > 25 [1].
>>
>> It
On Mon, 17 May 2021 18:23:41 GMT, Weijun Wang wrote:
> Please review this implementation of [JEP
> 411](https://openjdk.java.net/jeps/411).
>
> The code change is divided into 3 commits. Please review them one by one.
>
> 1.
>
On Sat, 15 May 2021 02:06:29 GMT, Sandhya Viswanathan
wrote:
>> This PR contains Short Vector Math Library support related changes for
>> [JEP-414 Vector API (Second Incubator)](https://openjdk.java.net/jeps/414),
>> in preparation for when targeted.
>>
>> Intel Short Vector Math Library
On Mon, 17 May 2021 18:23:41 GMT, Weijun Wang wrote:
> Please review this implementation of [JEP
> 411](https://openjdk.java.net/jeps/411).
>
> The code change is divided into 3 commits. Please review them one by one.
>
> 1.
>
Please review this implementation of [JEP
411](https://openjdk.java.net/jeps/411).
The code change is divided into 3 commits. Please review them one by one.
1.
https://github.com/openjdk/jdk/commit/576161d15423f58281e384174d28c9f9be7941a1
The essential change for this JEP, including the
On Thu, 13 May 2021 16:37:38 GMT, Vladimir Kozlov wrote:
> [JDK-8264806](https://bugs.openjdk.java.net/browse/JDK-8264806) changes
> removed sources and also removed JVMCI compiler from list of upgradable
> modules. JVMCI compiler modules should be upgradable in JDK to work with
> GraalVM.
>
On Thu, 13 May 2021 16:37:38 GMT, Vladimir Kozlov wrote:
> [JDK-8264806](https://bugs.openjdk.java.net/browse/JDK-8264806) changes
> removed sources and also removed JVMCI compiler from list of upgradable
> modules. JVMCI compiler modules should be upgradable in JDK to work with
> GraalVM.
>
On Thu, 13 May 2021 16:37:38 GMT, Vladimir Kozlov wrote:
> [JDK-8264806](https://bugs.openjdk.java.net/browse/JDK-8264806) changes
> removed sources and also removed JVMCI compiler from list of upgradable
> modules. JVMCI compiler modules should be upgradable in JDK to work with
> GraalVM.
>
On Thu, 13 May 2021 16:37:38 GMT, Vladimir Kozlov wrote:
> [JDK-8264806](https://bugs.openjdk.java.net/browse/JDK-8264806) changes
> removed sources and also removed JVMCI compiler from list of upgradable
> modules. JVMCI compiler modules should be upgradable in JDK to work with
> GraalVM.
>
On Mon, 17 May 2021 19:04:11 GMT, Jan Lahoda wrote:
>> This is a preview of a patch implementing JEP 406: Pattern Matching for
>> switch (Preview):
>> https://bugs.openjdk.java.net/browse/JDK-8213076
>>
>> The current draft of the specification is here:
>>
On Tue, 4 May 2021 20:48:34 GMT, Maurizio Cimadamore
wrote:
>> Jan Lahoda has updated the pull request incrementally with three additional
>> commits since the last revision:
>>
>> - Reflecting recent spec changes.
>> - Reflecting review comments.
>> - Reflecting review comments on
> This is a preview of a patch implementing JEP 406: Pattern Matching for
> switch (Preview):
> https://bugs.openjdk.java.net/browse/JDK-8213076
>
> The current draft of the specification is here:
> http://cr.openjdk.java.net/~gbierman/jep406/jep406-20210430/specs/patterns-switch-jls.html
>
> A
On 5/17/21 7:30 PM, erik.joels...@oracle.com wrote:
Oh, if it's double, we can just switch to using awk to make the
calculation, just like we do for TEST_JOBS. I just did a quick check and
it produces float values.
Oh, cool. Having a more precise MaxRAMPercentage would be nice.
--
Thanks,
On 2021-05-17 10:19, Aleksey Shipilev wrote:
On Mon, 17 May 2021 13:24:16 GMT, Jie Fu wrote:
Hi all,
vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java fails on our
many-core machines due to `-XX:MaxRAMPercentage=0`.
This is because `MaxRAMPercentage` will be always 0 if
On Mon, 17 May 2021 13:24:16 GMT, Jie Fu wrote:
> Hi all,
>
> vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java fails on our
> many-core machines due to `-XX:MaxRAMPercentage=0`.
> This is because `MaxRAMPercentage` will be always 0 if JTREG_JOBS > 25 [1].
>
> It can be reproduced
On Mon, 17 May 2021 16:55:35 GMT, Naoto Sato wrote:
> Please review the changes to the subject issue. java.util.Locale class has a
> long-standing issue for those obsolete ISO 639 languages where its
> normalization ends up in the obsolete codes. This change intends to flip the
>
On Mon, 17 May 2021 13:24:16 GMT, Jie Fu wrote:
> Hi all,
>
> vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java fails on our
> many-core machines due to `-XX:MaxRAMPercentage=0`.
> This is because `MaxRAMPercentage` will be always 0 if JTREG_JOBS > 25 [1].
>
> It can be reproduced
Please review the changes to the subject issue. java.util.Locale class has a
long-standing issue for those obsolete ISO 639 languages where its
normalization ends up in the obsolete codes. This change intends to flip the
normalization towards the current codes, providing a system property for
On Mon, 17 May 2021 13:24:16 GMT, Jie Fu wrote:
> Hi all,
>
> vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java fails on our
> many-core machines due to `-XX:MaxRAMPercentage=0`.
> This is because `MaxRAMPercentage` will be always 0 if JTREG_JOBS > 25 [1].
>
> It can be reproduced
On Mon, 17 May 2021 13:24:16 GMT, Jie Fu wrote:
> Hi all,
>
> vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java fails on our
> many-core machines due to `-XX:MaxRAMPercentage=0`.
> This is because `MaxRAMPercentage` will be always 0 if JTREG_JOBS > 25 [1].
>
> It can be reproduced
Hi all,
vmTestbase/vm/mlvm/anonloader/stress/oome/metaspace/Test.java fails on our
many-core machines due to `-XX:MaxRAMPercentage=0`.
This is because `MaxRAMPercentage` will be always 0 if JTREG_JOBS > 25 [1].
It can be reproduced by: `make test
On Sat, 15 May 2021 02:06:29 GMT, Sandhya Viswanathan
wrote:
>> This PR contains Short Vector Math Library support related changes for
>> [JEP-414 Vector API (Second Incubator)](https://openjdk.java.net/jeps/414),
>> in preparation for when targeted.
>>
>> Intel Short Vector Math Library
24 matches
Mail list logo
