> 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` > directly in `Thread.alive()`: > > boolean alive() { > return eetop != 0; > } > > I also updated a comment in relation to `eetop`. > > Testing: tiers 1-3 > > Thanks
David Holmes has updated the pull request incrementally with one additional commit since the last revision: Reformat comment block ------------- Changes: - all: https://git.openjdk.org/jdk/pull/13287/files - new: https://git.openjdk.org/jdk/pull/13287/files/d284547c..8e662cdf Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=13287&range=06 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=13287&range=05-06 Stats: 6 lines in 1 file changed: 0 ins; 0 del; 6 mod Patch: https://git.openjdk.org/jdk/pull/13287.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/13287/head:pull/13287 PR: https://git.openjdk.org/jdk/pull/13287