On 6/15/22 9:54 AM, Aleksey Shipilev wrote:
(I *suspect* that somewhere we stash the "current" thread onto stack,
and then remount to another thread, which makes "current" thread
obsolete. Assuming current thread does not change is quite pervasive,
and saving "current thread" on
> On 15 Jun 2022, at 17:54, Aleksey Shipilev wrote:
>
> Hi,
>
> Adding to the pile of port reports for Loom.
>
Hi Aleksey, and thank you for that great work!
>
> Anyhow, the choice between "ship x86_32 without VM continuations" or "ship
> x86_32 without C2" is obvious: VM continuations
On 16/06/2022 10:09, Aleksey Shipilev wrote:
On 6/15/22 20:26, Ron Pressler wrote:
Am I right to understand that to mean that the x86-32 port does fully
implement the virtual
threads spec, albeit with the “fake virtual thread” implementation
rather than VM continuations?
Yes. Although it is
On 6/16/22 10:38, dean.l...@oracle.com wrote:
On 6/15/22 9:54 AM, Aleksey Shipilev wrote:
(I *suspect* that somewhere we stash the "current" thread onto stack,
and then remount to another thread, which makes "current" thread
obsolete. Assuming current thread does not change is quite
On 6/15/22 20:26, Ron Pressler wrote:
Am I right to understand that to mean that the x86-32 port does fully implement
the virtual
threads spec, albeit with the “fake virtual thread” implementation rather than
VM continuations?
Yes. Although it is still not clear to me if that implementation
