Re: RFR: 8290041: ModuleDescriptor.hashCode is inconsistent [v2]

2022-08-15 Thread Jaikiran Pai
On Thu, 11 Aug 2022 14:16:51 GMT, Jaikiran Pai wrote: >> Can I please get a review of this change which proposes to fix >> https://bugs.openjdk.org/browse/JDK-8290041? >> >> As noted by the reporter, the current implementation is buggy since the >> calculation can result in a different value

Re: RFR: 8290041: ModuleDescriptor.hashCode is inconsistent [v3]

2022-08-15 Thread Jaikiran Pai
> Can I please get a review of this change which proposes to fix > https://bugs.openjdk.org/browse/JDK-8290041? > > As noted by the reporter, the current implementation is buggy since the > calculation can result in a different value of the hashcode depending on the > order of iteration of

Re: RFR: 8290041: ModuleDescriptor.hashCode is inconsistent [v2]

2022-08-15 Thread Jaikiran Pai
On Mon, 15 Aug 2022 16:07:45 GMT, Alan Bateman wrote: >> Jaikiran Pai has updated the pull request incrementally with one additional >> commit since the last revision: >> >> incorporate review comments and add more testing > > test/jdk/java/lang/module/ModuleDescriptorHashCodeTest.java line

Re: RFR: 8292327: java.io.EOFException in InflaterInputStream after JDK-8281962 [v2]

2022-08-15 Thread Volker Simonis
> The problem is that after > [JDK-8281962](https://bugs.openjdk.org/browse/JDK-8292327) we call `fill()` > unconditionally (and before calling `Inflater::inflate()`) in > `InflaterInputStream::read()` if `Inflater::needsInput()` is true. This > misses the case where the native inflater has

Re: RFR: 8292327: java.io.EOFException in InflaterInputStream after JDK-8281962

2022-08-15 Thread Volker Simonis
On Mon, 15 Aug 2022 18:36:11 GMT, Alan Bateman wrote: >> The problem is that after >> [JDK-8281962](https://bugs.openjdk.org/browse/JDK-8292327) we call `fill()` >> unconditionally (and before calling `Inflater::inflate()`) in >> `InflaterInputStream::read()` if `Inflater::needsInput()` is

Re: RFR: 8292327: java.io.EOFException in InflaterInputStream after JDK-8281962

2022-08-15 Thread Volker Simonis
On Mon, 15 Aug 2022 18:34:17 GMT, Alan Bateman wrote: >> The problem is that after >> [JDK-8281962](https://bugs.openjdk.org/browse/JDK-8292327) we call `fill()` >> unconditionally (and before calling `Inflater::inflate()`) in >> `InflaterInputStream::read()` if `Inflater::needsInput()` is

Re: RFR: 8292327: java.io.EOFException in InflaterInputStream after JDK-8281962

2022-08-15 Thread Volker Simonis
On Mon, 15 Aug 2022 18:01:15 GMT, Alan Bateman wrote: >> The problem is that after >> [JDK-8281962](https://bugs.openjdk.org/browse/JDK-8292327) we call `fill()` >> unconditionally (and before calling `Inflater::inflate()`) in >> `InflaterInputStream::read()` if `Inflater::needsInput()` is

Re: RFR: 8292350: Use static methods for hashCode/toString primitives

2022-08-15 Thread Roger Riggs
On Wed, 10 Aug 2022 08:01:41 GMT, Andrey Turbanov wrote: > It's a bit shorter and clearer. lgtm - Marked as reviewed by rriggs (Reviewer). PR: https://git.openjdk.org/jdk/pull/9816

Re: RFR: 8292016: Rework JLI_ReportErrorMessageSys [v8]

2022-08-15 Thread Julian Waters
> Second attempt at resolving > [JDK-8292016](https://bugs.openjdk.org/browse/JDK-8292016) with a less > intrusive approach this time > > Side note: While it might be preferred to remove this entirely, other areas > of the JDK also use the same flawed logic, and removing this would simply >

Re: RFR: 8291828: Reduce runtime of java.util.stream microbenchmarks

2022-08-15 Thread Eric Caspole
On Mon, 15 Aug 2022 14:32:51 GMT, Roger Riggs wrote: >> These changes reduce the default run time from about 1 day 22 hours to about >> 6 hours with good stability we can use in weekly testing. > > test/micro/org/openjdk/bench/java/util/stream/ops/value/SizedCount.java line > 30: > >> 28:

Re: RFR: 8292016: Rework JLI_ReportErrorMessageSys [v7]

2022-08-15 Thread Julian Waters
> Second attempt at resolving > [JDK-8292016](https://bugs.openjdk.org/browse/JDK-8292016) with a less > intrusive approach this time > > Side note: While it might be preferred to remove this entirely, other areas > of the JDK also use the same flawed logic, and removing this would simply >

Re: RFR: 8292327: java.io.EOFException in InflaterInputStream after JDK-8281962

2022-08-15 Thread Alan Bateman
On Mon, 15 Aug 2022 17:43:27 GMT, Volker Simonis wrote: > The problem is that after > [JDK-8281962](https://bugs.openjdk.org/browse/JDK-8292327) we call `fill()` > unconditionally (and before calling `Inflater::inflate()`) in > `InflaterInputStream::read()` if `Inflater::needsInput()` is

Re: RFR: 8292016: Rework JLI_ReportErrorMessageSys [v6]

2022-08-15 Thread Julian Waters
> Second attempt at resolving > [JDK-8292016](https://bugs.openjdk.org/browse/JDK-8292016) with a less > intrusive approach this time > > Side note: While it might be preferred to remove this entirely, other areas > of the JDK also use the same flawed logic, and removing this would simply >

RFR: 8292327: java.io.EOFException in InflaterInputStream after JDK-8281962

2022-08-15 Thread Volker Simonis
The problem is that after [JDK-8281962](https://bugs.openjdk.org/browse/JDK-8292327) we call `fill()` unconditionally (and before calling `Inflater::inflate()`) in `InflaterInputStream::read()` if `Inflater::needsInput()` is true. This misses the case where the native inflater has consumed all

Re: RFR: 8292016: Rework JLI_ReportErrorMessageSys [v5]

2022-08-15 Thread Julian Waters
> Second attempt at resolving > [JDK-8292016](https://bugs.openjdk.org/browse/JDK-8292016) with a less > intrusive approach this time > > Side note: While it might be preferred to remove this entirely, other areas > of the JDK also use the same flawed logic, and removing this would simply >

Re: RFR: 8291911: java/io/File/GetXSpace.java fails with "53687091200 != 161051996160"

2022-08-15 Thread Brian Burkhalter
On Fri, 12 Aug 2022 14:52:23 GMT, Brian Burkhalter wrote: > On Windows, suppress failure if the total space indicated by `df` is less > than `FileStore::getTotalSpace` and the free space indicated by `df` equals > `FileStore::getUnallocatedSpace`. In reality GetFreeDiskSpaceEx does not appear

Re: RFR: 8291911: java/io/File/GetXSpace.java fails with "53687091200 != 161051996160"

2022-08-15 Thread Brian Burkhalter
On Mon, 15 Aug 2022 16:39:42 GMT, Alan Bateman wrote: > This is hard to review. Would it be possible to provide a summary on the APIs > and df behave with quotas? We use the Windows API

Integrated: 8292196: Reduce runtime of java.util.regex microbenchmarks

2022-08-15 Thread Eric Caspole
On Fri, 12 Aug 2022 18:20:04 GMT, Eric Caspole wrote: > These changes reduce the run time to 45 minutes from about 1h40m with > stability good enough for weekly promo build testing. This pull request has now been integrated. Changeset: b5707b03 Author:Eric Caspole URL:

Re: RFR: 8291911: java/io/File/GetXSpace.java fails with "53687091200 != 161051996160"

2022-08-15 Thread Alan Bateman
On Fri, 12 Aug 2022 14:52:23 GMT, Brian Burkhalter wrote: > On Windows, suppress failure if the total space indicated by `df` is less > than `FileStore::getTotalSpace` and the free space indicated by `df` equals > `FileStore::getUnallocatedSpace`. This is hard to review. Would it be possible

Re: RFR: 8291118: [vectorapi] Optimize the implementation of lanewise FIRST_NONZERO

2022-08-15 Thread Paul Sandoz
On Fri, 29 Jul 2022 03:55:54 GMT, Xiaohong Gong wrote: > Vector API binary op "`FIRST_NONZERO`" represents the vector operation of "`a > != 0 ? a : b`", which can be implemented with existing APIs like "`compare + > blend`". The current implementation is more complex especially for the >

Re: RFR: 8290041: ModuleDescriptor.hashCode is inconsistent [v2]

2022-08-15 Thread Alan Bateman
On Thu, 11 Aug 2022 14:16:51 GMT, Jaikiran Pai wrote: >> Can I please get a review of this change which proposes to fix >> https://bugs.openjdk.org/browse/JDK-8290041? >> >> As noted by the reporter, the current implementation is buggy since the >> calculation can result in a different value

Re: RFR: 8291118: [vectorapi] Optimize the implementation of lanewise FIRST_NONZERO

2022-08-15 Thread Paul Sandoz
On Mon, 15 Aug 2022 01:10:54 GMT, Xiaohong Gong wrote: >> Vector API binary op "`FIRST_NONZERO`" represents the vector operation of >> "`a != 0 ? a : b`", which can be implemented with existing APIs like >> "`compare + blend`". The current implementation is more complex especially >> for the

Re: RFR: 8289049: x86_32 build fails with GCC 11 due to newString646_US warning [v3]

2022-08-15 Thread Alan Bateman
On Mon, 15 Aug 2022 13:56:38 GMT, Aleksey Shipilev wrote: >> See bug report for reproducer and error message. The warning looks quite >> superficial, and I initially suspected that it complains about `int len = >> (int)strlen(str)` cast of `size_t`. But what is confusing is nearly the >>

Re: RFR: 8292362: java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 failed on some platforms [v2]

2022-08-15 Thread Alan Bateman
On Mon, 15 Aug 2022 13:57:02 GMT, Ao Qi wrote: > > > Shouldn't we throw a SkippedException in this case? > > > > > > It's the child VM that skips so throwing SkippedException would require > > special handling in the parent. > > Like this? > > ``` > diff --git >

Re: RFR: 8292196: Reduce runtime of java.util.regex microbenchmarks

2022-08-15 Thread Roger Riggs
On Fri, 12 Aug 2022 18:20:04 GMT, Eric Caspole wrote: > These changes reduce the run time to 45 minutes from about 1h40m with > stability good enough for weekly promo build testing. Marked as reviewed by rriggs (Reviewer). - PR: https://git.openjdk.org/jdk/pull/9861

Re: RFR: 8291828: Reduce runtime of java.util.stream microbenchmarks

2022-08-15 Thread Roger Riggs
On Wed, 3 Aug 2022 16:28:31 GMT, Eric Caspole wrote: > These changes reduce the default run time from about 1 day 22 hours to about > 6 hours with good stability we can use in weekly testing. test/micro/org/openjdk/bench/java/util/stream/ops/value/SizedCount.java line 30: > 28: import

Re: RFR: 8289049: x86_32 build fails with GCC 11 due to newString646_US warning [v3]

2022-08-15 Thread Aleksey Shipilev
> See bug report for reproducer and error message. The warning looks quite > superficial, and I initially suspected that it complains about `int len = > (int)strlen(str)` cast of `size_t`. But what is confusing is nearly the > similar code in `newStringCp1252` apparently does not produce the

Re: RFR: 8292362: java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 failed on some platforms [v2]

2022-08-15 Thread Alan Bateman
On Mon, 15 Aug 2022 13:27:19 GMT, David Holmes wrote: > Shouldn't we throw a SkippedException in this case? It's the child VM that skips so throwing SkippedException would require special handling in the parent. - PR: https://git.openjdk.org/jdk/pull/9877

Integrated: 8292182: [TESTLIB] Enhance JAXPPolicyManager to setup required permissions for jtreg version 7 jar

2022-08-15 Thread Christian Stein
On Fri, 12 Aug 2022 16:26:30 GMT, Christian Stein wrote: > Enhance `JAXPPolicyManager` to setup required permissions for `jtreg` 7 by > accept version information in JAR file names. > > Find details in https://bugs.openjdk.org/browse/JDK-8292182 This pull request has now been integrated.

Re: RFR: 8292182: [TESTLIB] Enhance JAXPPolicyManager to setup required permissions for jtreg version 7 jar [v3]

2022-08-15 Thread Lance Andersen
On Sat, 13 Aug 2022 06:10:42 GMT, Christian Stein wrote: >> Enhance `JAXPPolicyManager` to setup required permissions for `jtreg` 7 by >> accept version information in JAR file names. >> >> Find details in https://bugs.openjdk.org/browse/JDK-8292182 > > Christian Stein has updated the pull

Re: RFR: 8292362: java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 failed on some platforms [v2]

2022-08-15 Thread David Holmes
On Mon, 15 Aug 2022 13:23:40 GMT, Ao Qi wrote: >> For example, java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 >> failed on LoongArch64 (probably other platforms unsupported in >> src/java.base/share/classes/jdk/internal/foreign/CABI.java might have the >> same issue): >> >>

Re: RFR: 8289049: x86_32 build fails with GCC 11 due to newString646_US warning [v2]

2022-08-15 Thread Alan Bateman
On Mon, 1 Aug 2022 14:50:48 GMT, Aleksey Shipilev wrote: >> See bug report for reproducer and error message. The warning looks quite >> superficial, and I initially suspected that it complains about `int len = >> (int)strlen(str)` cast of `size_t`. But what is confusing is nearly the >>

Re: RFR: 8292362: java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 failed on some platforms

2022-08-15 Thread Ao Qi
On Mon, 15 Aug 2022 12:59:59 GMT, Alan Bateman wrote: > Linker.nativeLinker is currently specified to throw UOE so you might find the > following will avoid ports needing to change the test less often: > > ``` > --- a/test/jdk/java/lang/Thread/jni/AttachCurrentThread/ImplicitAttach.java > +++

Re: RFR: 8292362: java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 failed on some platforms [v2]

2022-08-15 Thread Ao Qi
> For example, java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 > failed on LoongArch64 (probably other platforms unsupported in > src/java.base/share/classes/jdk/internal/foreign/CABI.java might have the > same issue): > > > Exception in thread "main"

Re: RFR: 8292362: java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 failed on some platforms

2022-08-15 Thread Alan Bateman
On Mon, 15 Aug 2022 12:23:41 GMT, Ao Qi wrote: > For example, java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 > failed on LoongArch64 (probably other platforms unsupported in > src/java.base/share/classes/jdk/internal/foreign/CABI.java might have the > same issue): > > >

RFR: 8292362: java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 failed on some platforms

2022-08-15 Thread Ao Qi
For example, java/lang/Thread/jni/AttachCurrentThread/AttachTest.java#id1 failed on LoongArch64 (probably other platforms unsupported in src/java.base/share/classes/jdk/internal/foreign/CABI.java might have the same issue): Exception in thread "main" java.lang.UnsupportedOperationException:

Re: RFR: 8292016: Rework JLI_ReportErrorMessageSys [v4]

2022-08-15 Thread Julian Waters
> Second attempt at resolving > [JDK-8292016](https://bugs.openjdk.org/browse/JDK-8292016) with a less > intrusive approach this time > > Side note: While it might be preferred to remove this entirely, other areas > of the JDK also use the same flawed logic, and removing this would simply >

Re: RFR: 8289049: x86_32 build fails with GCC 11 due to newString646_US warning [v2]

2022-08-15 Thread Aleksey Shipilev
On Mon, 1 Aug 2022 14:50:48 GMT, Aleksey Shipilev wrote: >> See bug report for reproducer and error message. The warning looks quite >> superficial, and I initially suspected that it complains about `int len = >> (int)strlen(str)` cast of `size_t`. But what is confusing is nearly the >>

Re: RFR: 8292350: Use static methods for hashCode/toString primitives

2022-08-15 Thread ExE Boss
On Wed, 10 Aug 2022 08:01:41 GMT, Andrey Turbanov wrote: > It's a bit shorter and clearer. Also, it avoids unnecessary boxing. - PR: https://git.openjdk.org/jdk/pull/9816

RFR: 8292350: Use static methods for hashCode/toString primitives

2022-08-15 Thread Andrey Turbanov
It's a bit shorter and clearer. - Commit messages: - [PATCH] Use static methods for hashCode/toString primitives Changes: https://git.openjdk.org/jdk/pull/9816/files Webrev: https://webrevs.openjdk.org/?repo=jdk=9816=00 Issue: https://bugs.openjdk.org/browse/JDK-8292350 Stats:

Re: RFR: 8292016: Rework JLI_ReportErrorMessageSys [v3]

2022-08-15 Thread Julian Waters
> Second attempt at resolving > [JDK-8292016](https://bugs.openjdk.org/browse/JDK-8292016) with a less > intrusive approach this time > > Side note: While it might be preferred to remove this entirely, other areas > of the JDK also use the same flawed logic, and removing this would simply >

Re: RFR: 8292016: Rework JLI_ReportErrorMessageSys [v2]

2022-08-15 Thread Julian Waters
> Second attempt at resolving > [JDK-8292016](https://bugs.openjdk.org/browse/JDK-8292016) with a less > intrusive approach this time > > Side note: While it might be preferred to remove this entirely, other areas > of the JDK also use the same flawed logic, and removing this would simply >