On Fri, 7 Mar 2025 06:19:03 GMT, Galder ZamarreƱo wrote:
>> This patch intrinsifies `Math.max(long, long)` and `Math.min(long, long)` in
>> order to help improve vectorization performance.
>>
>> Currently vectorization does not kick in for loops containing either of
>> these calls because of t
On Tue, 4 Jun 2024 07:47:46 GMT, SendaoYan wrote:
> Hi all,
> This PR several extra empty spaces and extra empty lines in several
> Makefiles. It's trivial fix, no risk.
>
> Thanks.
Looks good! Somehow the integrate command did not work.
-
Marked as reviewed by chagedorn (Revie
On Tue, 28 May 2024 14:01:44 GMT, Martin Doerr wrote:
> Fix obvious typo in micro benchmark.
Looks good and trivial!
-
Marked as reviewed by chagedorn (Reviewer).
PR Review: https://git.openjdk.org/jdk/pull/19427#pullrequestreview-2083086912
On Mon, 3 Jul 2023 07:13:14 GMT, Tobias Hartmann wrote:
> Backport of [JDK-8310829](https://bugs.openjdk.java.net/browse/JDK-8310829).
> Applies cleanly.
>
> Thanks,
> Tobias
Looks good.
-
Marked as reviewed by chagedorn (Reviewer).
PR Review: https://git.openjdk.org/jdk21/pull/
On Sat, 10 Jun 2023 12:25:57 GMT, Tobias Holenstein
wrote:
>> At the moment `CompileCommand` and `CompileOnly` use different syntax for
>> matching methods.
>>
>> ### Old CompileOnly format
>> - matching a **method name** with **class name** and **package name**:
>> `-XX:CompileOnly=package/p
On Fri, 9 Jun 2023 13:44:20 GMT, Tobias Holenstein
wrote:
>> At the moment `CompileCommand` and `CompileOnly` use different syntax for
>> matching methods.
>>
>> ### Old CompileOnly format
>> - matching a **method name** with **class name** and **package name**:
>> `-XX:CompileOnly=package/pa
On Fri, 9 Jun 2023 13:24:20 GMT, Tobias Holenstein
wrote:
>> At the moment `CompileCommand` and `CompileOnly` use different syntax for
>> matching methods.
>>
>> ### Old CompileOnly format
>> - matching a **method name** with **class name** and **package name**:
>> `-XX:CompileOnly=package/pa
On Wed, 24 May 2023 11:05:01 GMT, Tobias Holenstein
wrote:
>> Currently, errors during compile command parsing just print an error but
>> don't exit the VM. As a result, issues go unnoticed.
>>
>> With this PR the behavior is changed to exit the VM when an error occurs.
>>
>> E.g. `java -XX:
>> with `CompileOnly` and plug it into compile command file. Syntax used by
>> CompileOnly is also not very intuitive.
>>
>> `CompileOnly` is convenient because it's shorter to write and takes lists of
>> patterns, whereas `CompileCommand` only takes one patter
On Tue, 2 May 2023 11:35:54 GMT, Tobias Holenstein
wrote:
> Currently, errors during compile command parsing just print an error but
> don't exit the VM. As a result, issues go unnoticed.
>
> With this PR the behavior is changed to exit the VM when an error occurs.
>
> E.g. `java -XX:Compile
On Thu, 4 May 2023 13:36:22 GMT, Tobias Holenstein
wrote:
> At the moment `CompileCommand` and `CompileOnly` use different syntax for
> matching methods.
>
> ### Old CompileOnly format
> - matching a **method name** with **class name** and **package name**:
> `-XX:CompileOnly=package/path/Cla
11 matches
Mail list logo