On Tue, 31 May 2022 15:39: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
>>
On Tue, 31 May 2022 15:39: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
>>
On Tue, 31 May 2022 17:03:54 GMT, Aleksey Shipilev wrote:
> I expected this change to fix the broken ARM32 port, but it doesn't work.
There is work required to get the arm32 port working again, currently tracked
as JDK-828636 but there may be further issues beyond that.
-
PR:
On Tue, 31 May 2022 16:54:41 GMT, Boris Ulasevich
wrote:
> I expected this change to fix the broken ARM32 port, but it doesn't work.
It would not fix ARM32, because the interpreter stubs need to be predicated on
`Continuations::enabled()`. Also, as my ARM32 experiments show
On Tue, 31 May 2022 15:39: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
>>
> 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, the lack of continuations support means:
>
> 1. JVM TI
