RFR: 8286376: Wrong condition for using non-immediate oops on AArch64

[Erik Österlund]

With the introduction of loom, nmethod entry barriers were added for all GCs. So far, the use of nmethod entry barriers has implied that nmethod oops are patched in the instruction stream. That is no longer the case. A condition was added to make sure we still get non-immediate oops on AArch64 for collectors that use nmethod entry barriers, and support immediate oops. However, the condition was messed up, so we instead end up doing the wrong thing. We should do the right thing.

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

Commit messages:
 - 8286376: Wrong condition for using non-immediate oops on AArch64

Changes: https://git.openjdk.java.net/jdk/pull/8593/files
 Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=8593&range=00
  Issue: https://bugs.openjdk.java.net/browse/JDK-8286376
  Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
  Patch: https://git.openjdk.java.net/jdk/pull/8593.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/8593/head:pull/8593

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