On Tue, 31 May 2022 18:14:51 GMT, Chris Plummer wrote:
>> As part of the loom integration, jdb added `-trackvthreads` and the debug
>> agent added `enumeratevthreads`. These options are being renamed to
>> `-trackallthreads` and `includevirtualthreads` (the shorthand `vthreads`
>> should not h
On Tue, 31 May 2022 18:14:51 GMT, Chris Plummer wrote:
>> As part of the loom integration, jdb added `-trackvthreads` and the debug
>> agent added `enumeratevthreads`. These options are being renamed to
>> `-trackallthreads` and `includevirtualthreads` (the shorthand `vthreads`
>> should not h
On Wed, 1 Jun 2022 07:52:50 GMT, Andrey Turbanov wrote:
> `String.contains` was introduced in Java 5.
> Some code in jdk.hotspot.agent still uses old approach with `String.indexOf`
> to check if String contains specified substring.
> I propose to migrate such usages. Makes code shorter and easie
On Wed, 1 Jun 2022 07:52:50 GMT, Andrey Turbanov wrote:
> `String.contains` was introduced in Java 5.
> Some code in jdk.hotspot.agent still uses old approach with `String.indexOf`
> to check if String contains specified substring.
> I propose to migrate such usages. Makes code shorter and easie
On Thu, 2 Jun 2022 09:57:10 GMT, Andrey Turbanov wrote:
> > Please make sure you run the SA tests.
>
> This one, `test/hotspot/jtreg/serviceability` right?
You can just do the `test/hotspot/jtreg/serviceability/sa` subdirectory, but
there is also `test/jdk/sun/tools/jhsdb`
-
PR:
On Thu, 2 Jun 2022 09:54:31 GMT, Aleksey Shipilev wrote:
> [JDK-8287496](https://bugs.openjdk.java.net/browse/JDK-8287496) brought the
> alternative Loom implementation that can be used by ports as the fallback.
> That fallback does not support JVMTI entirely, so lots of tests fail. Some
> JVM
On Thu, 2 Jun 2022 09:54:31 GMT, Aleksey Shipilev wrote:
> [JDK-8287496](https://bugs.openjdk.java.net/browse/JDK-8287496) brought the
> alternative Loom implementation that can be used by ports as the fallback.
> That fallback does not support JVMTI entirely, so lots of tests fail. Some
> JVM
On Thu, 2 Jun 2022 14:32:28 GMT, Severin Gehwolf wrote:
> This adds a regression test for a recent fix (JDK-8287073). I've restructured
> the linux specific JDK code to call a separate static function to enable this
> test. It'll help future tests too.
>
> Testing:
> - [x] Container tests cont
On Thu, 2 Jun 2022 14:38:31 GMT, Aleksey Shipilev wrote:
> Trivial, or? I would like to have this integrated sooner to clean up our
> testing.
Ship it under trivial, thanks.
-
PR: https://git.openjdk.java.net/jdk/pull/8990
On Thu, 2 Jun 2022 09:54:31 GMT, Aleksey Shipilev wrote:
> [JDK-8287496](https://bugs.openjdk.java.net/browse/JDK-8287496) brought the
> alternative Loom implementation that can be used by ports as the fallback.
> That fallback does not support JVMTI entirely, so lots of tests fail. Some
> JVM
On Thu, 2 Jun 2022 09:54:31 GMT, Aleksey Shipilev wrote:
> [JDK-8287496](https://bugs.openjdk.java.net/browse/JDK-8287496) brought the
> alternative Loom implementation that can be used by ports as the fallback.
> That fallback does not support JVMTI entirely, so lots of tests fail. Some
> JVM
This adds a regression test for a recent fix (JDK-8287073). I've restructured
the linux specific JDK code to call a separate static function to enable this
test. It'll help future tests too.
Testing:
- [x] Container tests continue to pass + GHA
- [x] New regression test fails prior the code fix
Please review this PR for fixing JDK-8287281.
I chose a different solution than the one suggested. Looking at all callers of
`Handshake::execute`, it seems that only one depends on `target == current`.
The rest special case that by calling `is_handshake_safe_for` and `do_thread`
directly. I co
On Thu, 2 Jun 2022 13:47:23 GMT, Johan Sjölén wrote:
> Please review this PR for fixing JDK-8287281.
>
> I chose a different solution than the one suggested. Looking at all callers
> of `Handshake::execute`, it seems that only one depends on `target ==
> current`. The rest special case that by
On Thu, 2 Jun 2022 09:54:31 GMT, Aleksey Shipilev wrote:
> [JDK-8287496](https://bugs.openjdk.java.net/browse/JDK-8287496) brought the
> alternative Loom implementation that can be used by ports as the fallback.
> That fallback does not support JVMTI entirely, so lots of tests fail. Some
> JVM
On Thu, 2 Jun 2022 09:54:31 GMT, Aleksey Shipilev wrote:
> [JDK-8287496](https://bugs.openjdk.java.net/browse/JDK-8287496) brought the
> alternative Loom implementation that can be used by ports as the fallback.
> That fallback does not support JVMTI entirely, so lots of tests fail. Some
> JVM
On Thu, 2 Jun 2022 11:05:30 GMT, Alan Bateman wrote:
> I expect you can unexclude the runtime/* tests from this section too. Also
> the same section in test/jdk/ProblemList.txt that excludes the tests on
> x86_32 can be cleaned up too, maybe a separate PR.
Yes, in separate PR. In this PR, I wa
On Thu, 2 Jun 2022 09:54:31 GMT, Aleksey Shipilev wrote:
> [JDK-8287496](https://bugs.openjdk.java.net/browse/JDK-8287496) brought the
> alternative Loom implementation that can be used by ports as the fallback.
> That fallback does not support JVMTI entirely, so lots of tests fail. Some
> JVM
On Wed, 1 Jun 2022 20:59:41 GMT, Chris Plummer wrote:
> Please make sure you run the SA tests.
This one, `test/hotspot/jtreg/serviceability` right?
-
PR: https://git.openjdk.java.net/jdk/pull/8966
[JDK-8287496](https://bugs.openjdk.java.net/browse/JDK-8287496) brought the
alternative Loom implementation that can be used by ports as the fallback. That
fallback does not support JVMTI entirely, so lots of tests fail. Some JVMTI is
still supported, so cutting off at `@requires vm.jvmti` seems
On Wed, 1 Jun 2022 06:04:14 GMT, Alan Bateman wrote:
>> This patch adds an alternative virtual thread implementation where each
>> virtual thread is backed by an OS thread. It doesn't scale but it can be
>> used by ports that don't have continuations support in the VM. Aside from
>> scalabilit
On Sun, 29 May 2022 14:46:39 GMT, Alan Bateman wrote:
> This patch adds an alternative virtual thread implementation where each
> virtual thread is backed by an OS thread. It doesn't scale but it can be used
> by ports that don't have continuations support in the VM. Aside from
> scalability,
22 matches
Mail list logo
