RFR: 8282475: SafeFetch should not rely on existence of Thread::current [v4]

[Johannes Bechberger]

On Wed, 9 Mar 2022 10:11:06 GMT, Thomas Stuefe <stuefe at openjdk.org> wrote:

> Call sites in shared code are now easier to mentally parse. os::disable_jit_calls_for_current_thread() is much clearer than MACOS_AARCH64_ONLY(os::ThreadWX::Enable __wx(os::ThreadWX::Write));

That's not enough, as I wrote before, the RAII object is still needed for nesting. But I agree, that using better names would improve readability (like having two RAII objects for specific purposes).

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

PR: https://git.openjdk.java.net/jdk/pull/7727