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

[David Holmes]

On Mon, 21 Mar 2022 12:44:58 GMT, Thomas Stuefe <stuefe at openjdk.org> wrote:

>> Johannes Bechberger has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   Remove two unnecessary lines
>
> I'm currently implementing Andrews proposal for a static safefetch (https://github.com/openjdk/jdk/pull/7865, still in draft, but almost done). That will be more generic solution since we don't have to deal with thread wx state at all. That's why we closed this PR.

The conversation here is some what hard to follow. I do see that "foreign threads" was mentioned by @tstuefe  in the context of AGCT but I have to assume he misspoke there (assuming a foreign thread is one not attached to the VM) as AGCT only works for attached JavaThreads. The signal handler that will call AGCT has to be prepared to find any kind of thread in any state, but AGCT should only be called on the right kinds of thread in the right state.

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

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