On Tue, 9 May 2023 22:14:04 GMT, Erik Joelsson wrote:
> I think you also need to make a change to `GraalBuilderImage.gmk` and the
> target in `Main.gmk` that calls it.
Good catch! Fixed `GraalBuilderImage.gmk`, thanks!
For the `graal-builder-image` target that uses `GraalBuilderImage.gmk`,
> This PR is branched from the makefile changes for
> https://bugs.openjdk.org/browse/JDK-8303796 and contains the following for
> handling the JDK/hotspot static libraries:
>
> - Introduce new make target(s) for creating image/bundle containing hotspot
> libjvm.a and JDK static libraries
>
>
On Tue, 9 May 2023 21:46:42 GMT, Jiangli Zhou wrote:
>> This PR is branched from the makefile changes for
>> https://bugs.openjdk.org/browse/JDK-8303796 and contains the following for
>> handling the JDK/hotspot static libraries:
>>
>> - Introduce new make target(s) for creating image/bundle
On Tue, 9 May 2023 20:43:13 GMT, Phil Race wrote:
> I want to work through the scenarios and how much of it is specific to the
> behaviours of the API you are using and so forth. Since you use the
> Preferences API for saving the token, if you keyed it off the Robot class
> rather than the
On Mon, 8 May 2023 19:45:18 GMT, Jiangli Zhou wrote:
> > > All of that said, I think we can get away with a smaller subset of
> > > targets and deliverables. AFAIK, graal needs the combined
> > > `graal-builder-image` as input to their build anyway, so they should not
> > > have any
> This PR is branched from the makefile changes for
> https://bugs.openjdk.org/browse/JDK-8303796 and contains the following for
> handling the JDK/hotspot static libraries:
>
> - Introduce new make target(s) for creating image/bundle containing hotspot
> libjvm.a and JDK static libraries
>
>
> This PR is branched from the makefile changes for
> https://bugs.openjdk.org/browse/JDK-8303796 and contains the following for
> handling the JDK/hotspot static libraries:
>
> - Introduce new make target(s) for creating image/bundle containing hotspot
> libjvm.a and JDK static libraries
>
>
On Fri, 5 May 2023 12:34:29 GMT, Jan Lahoda wrote:
>> To support JShell and other usecases, the JDK uses JLine, which provides
>> line-editing functionality inside a terminal.
>>
>> JLine has several ways to work with the terminal, based on various
>> additional libraries and tools. Most of
On Fri, 5 May 2023 14:35:46 GMT, Alexander Zvegintsev
wrote:
>> Modern Linux systems often come with
>> [Wayland](https://wayland.freedesktop.org/) by default.
>> This comes with some difficulties, and one of them is the inability to get
>> screenshots from the system.
>> This is because we
On Mon, 8 May 2023 20:05:50 GMT, Chen Liang wrote:
>> This patch replaces `FIXPATH` with `FixPath` on individual path argumenets.
>> The root cause might be that JMH requires passing VM args to benchmarks in
>> quotes, which might have triggered incorrect detections in `FIXPATH` (as in
>>
On Mon, 8 May 2023 20:05:50 GMT, Chen Liang wrote:
>> This patch replaces `FIXPATH` with `FixPath` on individual path argumenets.
>> The root cause might be that JMH requires passing VM args to benchmarks in
>> quotes, which might have triggered incorrect detections in `FIXPATH` (as in
>>
On Tue, 9 May 2023 03:11:10 GMT, Chen Liang wrote:
> Please review this simple patch that fixes the package determination for
> nested classes in the `@sealedGraph` taglet.
>
> Current JDK 21:
>
On Mon, 8 May 2023 20:05:50 GMT, Chen Liang wrote:
>> This patch replaces `FIXPATH` with `FixPath` on individual path argumenets.
>> The root cause might be that JMH requires passing VM args to benchmarks in
>> quotes, which might have triggered incorrect detections in `FIXPATH` (as in
>>
On Mon, 8 May 2023 20:05:50 GMT, Chen Liang wrote:
>> This patch replaces `FIXPATH` with `FixPath` on individual path argumenets.
>> The root cause might be that JMH requires passing VM args to benchmarks in
>> quotes, which might have triggered incorrect detections in `FIXPATH` (as in
>>
On Tue, 9 May 2023 12:55:42 GMT, Stefan Karlsson wrote:
>> Hi all,
>>
>> Please review the implementation of Generational ZGC, which can be turned on
>> by adding -XX:+ZGenerational in addition to using -XX:+UseZGC. Generational
>> ZGC is a major rewrite of the non-generational ZGC version
On Mon, 8 May 2023 18:41:56 GMT, Sergey Bylokhov wrote:
> > It seems that the current robot API is not suitable for this.
>
> Can we just reset the token when we create a new instance of Robot?
This will be a big problem for automated testing, as each test with the robot
will require user
On Tue, 9 May 2023 10:38:54 GMT, Johannes Bechberger
wrote:
> Fixes the issue by adding `--add-exports` for the required modules and making
> the `HttpHeaderParser` final (fixing an issue with calling overridable
> methods in a constructor).
Marked as reviewed by djelinski (Reviewer).
> Hi all,
>
> Please review the implementation of Generational ZGC, which can be turned on
> by adding -XX:+ZGenerational in addition to using -XX:+UseZGC. Generational
> ZGC is a major rewrite of the non-generational ZGC version that exists in the
> openjdk/jdk repository. It splits the heap
On Tue, 9 May 2023 10:38:54 GMT, Johannes Bechberger
wrote:
> Fixes the issue by adding `--add-exports` for the required modules and making
> the `HttpHeaderParser` final (fixing an issue with calling overridable
> methods in a constructor).
Marked as reviewed by erikj (Reviewer).
> Hi all,
>
> Please review the implementation of Generational ZGC, which can be turned on
> by adding -XX:+ZGenerational in addition to using -XX:+UseZGC. Generational
> ZGC is a major rewrite of the non-generational ZGC version that exists in the
> openjdk/jdk repository. It splits the heap
On Tue, 9 May 2023 10:38:54 GMT, Johannes Bechberger
wrote:
> Fixes the issue by adding `--add-exports` for the required modules and making
> the `HttpHeaderParser` final (fixing an issue with calling overridable
> methods in a constructor).
Well, I wanted to use the WhiteBox testing API for
On Tue, 9 May 2023 10:38:54 GMT, Johannes Bechberger
wrote:
> Fixes the issue by adding `--add-exports` for the required modules and making
> the `HttpHeaderParser` final (fixing an issue with calling overridable
> methods in a constructor).
That's interesting. How did you find this? Is the
Fixes the issue by adding `--add-exports` for the required modules and making
the `HttpHeaderParser` final (fixing an issue with calling overridable methods
in a constructor).
-
Commit messages:
- Fix make build-test-lib
Changes: https://git.openjdk.org/jdk/pull/13885/files
On Tue, 9 May 2023 07:27:46 GMT, Kim Barrett wrote:
>> Stefan Karlsson has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Workaround failed reservation in ZForwardingTest
>
> src/hotspot/share/code/relocInfo.hpp line 1105:
>
>> 1103:
On Tue, 9 May 2023 06:06:11 GMT, Stefan Karlsson wrote:
>> Hi all,
>>
>> Please review the implementation of Generational ZGC, which can be turned on
>> by adding -XX:+ZGenerational in addition to using -XX:+UseZGC. Generational
>> ZGC is a major rewrite of the non-generational ZGC version
On Tue, 9 May 2023 03:11:10 GMT, Chen Liang wrote:
> Please review this simple patch that fixes the package determination for
> nested classes in the `@sealedGraph` taglet.
>
> Current JDK 21:
>
On Tue, 9 May 2023 00:50:56 GMT, Fei Yang wrote:
>> That's unfortunate. Could you try this patch, which probes the address range
>> to see if it can reserve the memory somewhere else within
>> `[ZAddressHeapBase, ZAddressHeapBase+ZAddressOffsetMax)`:
>>
> Hi all,
>
> Please review the implementation of Generational ZGC, which can be turned on
> by adding -XX:+ZGenerational in addition to using -XX:+UseZGC. Generational
> ZGC is a major rewrite of the non-generational ZGC version that exists in the
> openjdk/jdk repository. It splits the heap
28 matches
Mail list logo
