On Fri, 20 Oct 2023 19:18:47 GMT, Matthew Donovan wrote:
> Hello,
>
> In this PR I removed NSS tests from the ProblemList and updated NssTest to
> use Sqlite databases. I also removed code in PKCS11Test.java that falls back
> to NSS libraries installed on the test system. The tests can still
On Fri, 20 Oct 2023 15:45:50 GMT, Doug Simon wrote:
>> The Graal code base has
>> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
>> its module to `jdk.compiler.graal` as part of preparations for Project
>> Galahad. Due to the way Java modules work,
Hello,
In this PR I removed NSS tests from the ProblemList and updated NssTest to use
Sqlite databases. I also removed code in PKCS11Test.java that falls back to NSS
libraries installed on the test system. The tests can still be run with
different NSS libraries but they have to be specified by
On Fri, 20 Oct 2023 15:45:50 GMT, Doug Simon wrote:
>> The Graal code base has
>> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
>> its module to `jdk.compiler.graal` as part of preparations for Project
>> Galahad. Due to the way Java modules work,
On Fri, 20 Oct 2023 15:45:50 GMT, Doug Simon wrote:
>> The Graal code base has
>> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
>> its module to `jdk.compiler.graal` as part of preparations for Project
>> Galahad. Due to the way Java modules work,
This fixes the links to nested classes like `ValueLayout.OfLong` in the
rendered sealed class hierarchy graph.
A similar problem with nested classes exist for `@sealedGraph` on them, where
their graphs will be generated to a wrong directory and the graph link broken,
as seen in
On Fri, 20 Oct 2023 14:25:30 GMT, Magnus Ihse Bursie wrote:
> Unfortunately, [JDK-8317039](https://bugs.openjdk.org/browse/JDK-8317039)
> caused a regression. The `$(JAVA)` variable did not just contain a path,
> which was assumed by the patch, but also the necessary flags in
>
On Fri, 20 Oct 2023 13:46:35 GMT, Magnus Ihse Bursie wrote:
>> Indeed, I see no reason to rush the integration for this before we've
>> resolved the failing test.
>>
>> I can confirm that outside of the context of GHA, the `test-prebuilt` target
>> does not properly resolve _relative_ paths
On Fri, 20 Oct 2023 15:45:50 GMT, Doug Simon wrote:
>> The Graal code base has
>> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
>> its module to `jdk.compiler.graal` as part of preparations for Project
>> Galahad. Due to the way Java modules work,
On Fri, 20 Oct 2023 15:32:55 GMT, Doug Simon wrote:
>> The Graal code base has
>> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
>> its module to `jdk.compiler.graal` as part of preparations for Project
>> Galahad. Due to the way Java modules work,
On Fri, 20 Oct 2023 15:32:55 GMT, Doug Simon wrote:
>> The Graal code base has
>> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
>> its module to `jdk.compiler.graal` as part of preparations for Project
>> Galahad. Due to the way Java modules work,
> The Graal code base has
> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
> its module to `jdk.compiler.graal` as part of preparations for Project
> Galahad. Due to the way Java modules work, this requires a JDK change. The
> core of the issue is
> The Graal code base has
> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
> its module to `jdk.compiler.graal` as part of preparations for Project
> Galahad. Due to the way Java modules work, this requires a JDK change. The
> core of the issue is
On Fri, 13 Oct 2023 16:28:19 GMT, Doug Simon wrote:
> The Graal code base has
> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
> its module to `jdk.compiler.graal` as part of preparations for Project
> Galahad. Due to the way Java modules work, this
On Fri, 20 Oct 2023 14:27:43 GMT, Vladimir Kozlov wrote:
> Why you replaced pair of copyright years with one year in module-info.Java
> files? Instead of updating last year only. Why also update 'since' there?
> Even if you changed location these files existed already.
The files may be
Unfortunately, [JDK-8317039](https://bugs.openjdk.org/browse/JDK-8317039)
caused a regression. The `$(JAVA)` variable did not just contain a path, which
was assumed by the patch, but also the necessary flags in `$(JAVA_FLAGS)`.
Furthermore, the original implementation deviated from how we
On Fri, 13 Oct 2023 16:28:19 GMT, Doug Simon wrote:
> The Graal code base has
> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
> its module to `jdk.compiler.graal` as part of preparations for Project
> Galahad. Due to the way Java modules work, this
On Wed, 11 Oct 2023 10:00:14 GMT, Frederic Thevenet
wrote:
>> Frederic Thevenet has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Added a test to verify that symbols are available
>
> Indeed, I see no reason to rush the integration for
On Fri, 13 Oct 2023 16:28:19 GMT, Doug Simon wrote:
> The Graal code base has
> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
> its module to `jdk.compiler.graal` as part of preparations for Project
> Galahad. Due to the way Java modules work, this
On Fri, 13 Oct 2023 16:28:19 GMT, Doug Simon wrote:
> The Graal code base has
> [renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
> its module to `jdk.compiler.graal` as part of preparations for Project
> Galahad. Due to the way Java modules work, this
The Graal code base has
[renamed](https://github.com/oracle/graal/commit/1e41203d10db321f86723eac90f6cd0573b08b33)
its module to `jdk.compiler.graal` as part of preparations for Project
Galahad. Due to the way Java modules work, this requires a JDK change. The core
of the issue is that the
On Thu, 19 Oct 2023 13:49:21 GMT, Robbin Ehn wrote:
>> Hi please consider.
>>
>> This works with 2.30, 2.34, 2.38, 2.39, 2.40, 2.41 and current master head.
>> (tested x64 and some RV)
>>
>> There are 4 changes in binutils we work around.
>> - zstd compressed debug sections
>> - libsframe
On Thu, 19 Oct 2023 13:49:21 GMT, Robbin Ehn wrote:
>> Hi please consider.
>>
>> This works with 2.30, 2.34, 2.38, 2.39, 2.40, 2.41 and current master head.
>> (tested x64 and some RV)
>>
>> There are 4 changes in binutils we work around.
>> - zstd compressed debug sections
>> - libsframe
On Tue, 5 Sep 2023 07:53:36 GMT, Afshin Zafari wrote:
> A new benchmark for measuring the NMT overhead in `summary` and `detail`
> modes.
> The tests are run using:
>
> make CONF=debug test TEST="micro:java.vm.runtime.NMTBenchmark"
> MICRO="RESULTS_FORMAT=json"
>
> The results are written
> Classfile API is an internal library under package `jdk.internal.classfile`
> in JDK 21.
> This pull request turns the Classfile API into a preview feature and moves it
> into `java.lang.classfile`.
> It repackages all uses across JDK and tests and adds lots of missing Javadoc.
>
> This PR
On Thu, 19 Oct 2023 13:49:21 GMT, Robbin Ehn wrote:
>> Hi please consider.
>>
>> This works with 2.30, 2.34, 2.38, 2.39, 2.40, 2.41 and current master head.
>> (tested x64 and some RV)
>>
>> There are 4 changes in binutils we work around.
>> - zstd compressed debug sections
>> - libsframe
On Thu, 19 Oct 2023 17:08:20 GMT, Aleksey Shipilev wrote:
> Simple fix to allow running `.jasm` tests directly, like we can do now with
> `.java` and `.sh` tests.
>
> Before the fix:
>
>
> % make images test TEST=runtime/clone/LocalClone.jasm
> Test selection 'runtime/clone/LocalClone.jasm',
On Thu, 19 Oct 2023 17:08:20 GMT, Aleksey Shipilev wrote:
> Simple fix to allow running `.jasm` tests directly, like we can do now with
> `.java` and `.sh` tests.
>
> Before the fix:
>
>
> % make images test TEST=runtime/clone/LocalClone.jasm
> Test selection 'runtime/clone/LocalClone.jasm',
On Thu, 19 Oct 2023 13:49:21 GMT, Robbin Ehn wrote:
>> Hi please consider.
>>
>> This works with 2.30, 2.34, 2.38, 2.39, 2.40, 2.41 and current master head.
>> (tested x64 and some RV)
>>
>> There are 4 changes in binutils we work around.
>> - zstd compressed debug sections
>> - libsframe
29 matches
Mail list logo
