[Test] create a suitable HotSpot testing group for CVM

[luchsh]

CompoundVM is not and should not be 100% compatible with any existing major OpenJDK specifications, but a suitable sub-set of HotSpot tests to validate VM functionalities is still mandatory.

[duanyangjing]

#109 has a backported gc test, more hotspot tests need to be enabled later

[duanyangjing]

Tests fixed by PRs

#129 Remaining failures: 187 x64, 188 aarch64
#123 Remaining failures: 180 x64, 187 aarch64
#131 Remaining failures: 180 x64, 176 aarch64
#122 Remaining failures: 146 x64, 154 aarch64
#127 Remaining failures: 143 x64, 150 aarch64
#132 Remaining failures: 140 x64, 147 aarch64
#135 Remaining failures: 131 x64, 138 aarch64
#136 Remaining failures: 125 x64, 132 aarch64

---

Tests that can be skipped in jtreg_hotspot8_excludes_x64.list‎

6 tests in compiler/intrinsics/sha/sanity/. These tests can pass on physical machines, in container environment some cpu features are not available.
5 tests in compiler/tiered. These tests are related to internal heuristics about "trivial" methods

Tests that can be skipped in jtreg_hotspot8_excludes_aarch64.list‎

6 tests in compiler/intrinsics/sha/sanity/, these tests can pass on physical machines, in container environment some cpu features are not available.
5 tests in compiler/tiered. These tests are related to internal heuristics about "trivial" methods

RTM only supported in x64

compiler/rtm/cli/TestPrintPreciseRTMLockingStatisticsOptionOnUnsupportedConfig.java
compiler/rtm/cli/TestRTMAbortRatioOptionOnUnsupportedConfig.java
compiler/rtm/cli/TestRTMAbortThresholdOption.java
compiler/rtm/cli/TestRTMLockingCalculationDelayOption.java
compiler/rtm/cli/TestRTMLockingThresholdOption.java
compiler/rtm/cli/TestRTMRetryCountOption.java
compiler/rtm/cli/TestRTMSpinLoopCountOption.java
compiler/rtm/cli/TestRTMTotalCountIncrRateOptionOnUnsupportedConfig.java
compiler/rtm/cli/TestUseRTMDeoptOptionOnUnsupportedConfig.java
compiler/rtm/cli/TestUseRTMForStackLocksOptionOnUnsupportedConfig.java
compiler/rtm/cli/TestUseRTMXendForLockBusyOption.java

[duanyangjing]

Test compiler/7196199/Test7196199.java failure caused by the following different behavior:

➜  java ~/work/java/cvm-opensource/jdk17u/output/CompoundVM_8.17.3_linux_x64/bin/java -server -XX:+IgnoreUnrecognizedVMOptions -XX:GuaranteedSafepointInterval=100 -version
openjdk version "1.8.0_452"
OpenJDK Runtime Environment (build 1.8.0_452-cvm-b00)
OpenJDK 64-Bit Server VM (build 25.452-b00, mixed mode)
➜  java ~/work/java/cvm-opensource/jdk17u/output/CompoundVM_8.17.3_linux_x64/bin/java -cvm -XX:+IgnoreUnrecognizedVMOptions -XX:GuaranteedSafepointInterval=100 -version
Error: VM option 'GuaranteedSafepointInterval' is diagnostic and must be enabled via -XX:+UnlockDiagnosticVMOptions.
Error: The unlock option must precede 'GuaranteedSafepointInterval'.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Test pass if we run the hotspot17 version of this test, other tests include:

compiler/6859338/Test6859338.java
compiler/7196199/Test7196199.java
compiler/intrinsics/sha/sanity/TestSHA1Intrinsics.java
compiler/intrinsics/sha/sanity/TestSHA1MultiBlockIntrinsics.java
compiler/tiered/ConstantGettersTransitionsTest.java
compiler/tiered/LevelTransitionTest.java
compiler/tiered/TieredLevelsTest.java
compiler/whitebox/EnqueueMethodForCompilationTest.java
compiler/whitebox/GetNMethodTest.java
compiler/whitebox/MakeMethodNotCompilableTest.java
serviceability/ParserTest.java

[duanyangjing]

Following tests fail just because they expect different warning message between jdk8 and jdk17

compiler/intrinsics/sha/cli/TestUseSHA1IntrinsicsOptionOnUnsupportedCPU.java
compiler/intrinsics/sha/cli/TestUseSHA256IntrinsicsOptionOnUnsupportedCPU.java
compiler/intrinsics/sha/cli/TestUseSHA512IntrinsicsOptionOnUnsupportedCPU.java
compiler/intrinsics/sha/cli/TestUseSHAOptionOnUnsupportedCPU.java

➜  java ~/work/java/cvm-opensource/jdk17u/output/CompoundVM_8.17.3_linux_x64/bin/java -server -XX:+UseSHA1Intrinsics -version
OpenJDK 64-Bit Server VM warning: SHA intrinsics are not available on this CPU
openjdk version "1.8.0_452"
OpenJDK Runtime Environment (build 1.8.0_452-cvm-b00)
OpenJDK 64-Bit Server VM (build 25.452-b00, mixed mode)
➜  java ~/work/java/cvm-opensource/jdk17u/output/CompoundVM_8.17.3_linux_x64/bin/java -cvm -XX:+UseSHA1Intrinsics -version
OpenJDK 64-Bit Server VM (CompoundVM 8.17.3) warning: Intrinsics for SHA-1 crypto hash functions not available on this CPU.
openjdk version "1.8.0_452"
OpenJDK Runtime Environment (build 1.8.0_452-cvm-b00)
OpenJDK 64-Bit Server VM (CompoundVM 8.17.3) (build 17.0.16+0, mixed mode)

[duanyangjing]

TestG1HeapRegionSize.java fails because G1HeapRegionSize has size restriction in jdk17.

Suggested fix: change test source code

<  * @run main/othervm -XX:G1HeapRegionSize=64m -Xmx256m TestG1HeapRegionSize 33554432
---
>  * @run main/othervm -XX:G1HeapRegionSize=32m -Xmx256m TestG1HeapRegionSize 33554432