On Thu, 30 Oct 2025 21:10:18 GMT, Dean Long <[email protected]> wrote:

> Re: SafeFetch, it is probably OK to make NativePostCallNop_at slightly slower 
> for uses like make_deoptimized(), but the oopmap optimizations like 
> CodeCache::find_blob_and_oopmap() were highly optimized to make 
> loom/VirtualThread performance reasonable. Adding a SafeFetch here might 
> cause a regression.

Sure, but 2 things:
Loom doesn't meed post-call NOPs as much as it used to.
We could fairly easily make SafeFetch much faster than it is, if needs be.
But anyway, I approved this patch.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/26678#issuecomment-3476017720

Reply via email to