Re: RFR: 8305425: Thread.isAlive0 doesn't need to call into the VM [v3]

2023-04-04 Thread David Holmes
On Tue, 4 Apr 2023 09:22:29 GMT, Aleksey Shipilev wrote: >> David Holmes has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Ensure HB relationship exists; additional explanatory comments > > src/java.base/share/classes/java/lang/Thread.java

Re: RFR: 8305425: Thread.isAlive0 doesn't need to call into the VM [v3]

2023-04-04 Thread Aleksey Shipilev
On Mon, 3 Apr 2023 22:41:44 GMT, David Holmes wrote: >> We have the strange situation where calling `t.isAlive()` on a >> `java.lang.Thread` `t`, will call into the VM (via `alive()` then >> `isAlive0()`) where the VM then examines the `eetop` field of `t` to extract >> its `JavaThread` pointe

Re: RFR: 8305425: Thread.isAlive0 doesn't need to call into the VM [v3]

2023-04-03 Thread David Holmes
> We have the strange situation where calling `t.isAlive()` on a > `java.lang.Thread` `t`, will call into the VM (via `alive()` then > `isAlive0()`) where the VM then examines the `eetop` field of `t` to extract > its `JavaThread` pointer and compare it to null. We can simply read `eetop` > dir