Single Thread Continuation

[Attila Kelemen]

>
>
> 2. We need to synchronize access to mutable state to avoid memory
>    hazards. This is a separate issue from synchronizing access to
>    mutable state to avoid correctness issues. With virtual threads on
>    a single platform thread, this goes away too (because it's always
>    the same thread observing memory operations; no barriers needed).
>
>
That still seems incorrect to me (in principle, in practice it most likely
will end up to be fine, but I just wouldn't rely on it), because the
barrier is needed to prevent instruction reordering by the compiler, and
you are not safe from that by using the same platform thread.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20230703/25a81a9f/attachment.htm>