[jdk11u-dev] RFR: 8253015: Aarch64: Move linux code out from generic CPU feature detection [v4]

[openjdk-notifier [bot]]

On Mon, 4 Oct 2021 16:38:28 GMT, Reka Kovacs <github.com+25946952+rnkovacs at openjdk.org> wrote:

>> Not a clean backport. Differences to the original commit:
>> 
>> - Changes to files under `src/hotspot/cpu/aarch64/` and `src/hotspot/os_cpu/linux_aarch64/` are adjusted to cover hardware features supported in JDK 11.
>> - As JDK 11 is built using an older C++ standard than tip, `static_assert`s need to be replaced with `STATIC_ASSERT` macros in `vm_version_linux_aarch64.cpp`.
>> - The GraalVM related changes in `vmStructs_jvmci.cpp`, `AArch64HotSpotLIRGenerator.java` and `GraalHotSpotVMConfig.java` are skipped as they seem to be modifying code added in JDK 14 ([JDK-8226222](https://bugs.openjdk.java.net/browse/JDK-8226222) and [JDK-8231973](https://bugs.openjdk.java.net/browse/JDK-8229201)).
>> 
>> This is part of the Windows/AArch64 port.
>
> Reka Kovacs has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits:
> 
>  - Backport 36998b006d6a9ee8145004778534d1f35a55e068
>  - Backport ec9bee68660acd6abf0b4dd4023ae69514542256

The dependent pull request has now been integrated, and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:


git checkout 8250810-push-missing
git fetch https://git.openjdk.java.net/jdk11u-dev master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

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

PR: https://git.openjdk.java.net/jdk11u-dev/pull/299