Open Akira1Saitoh opened 2 years ago
@gita-omr FYI
Just for the record, the jdk_vector
temporarily set the concurrency to 1 on linux_aarch64 (see https://github.com/adoptium/aqa-tests/pull/4119). Once the current issue is resolved, we should revert https://github.com/adoptium/aqa-tests/pull/4119.
Can we close this issue considering https://github.com/adoptium/aqa-tests/pull/4189 ?
Unfortunately, we cannot. https://github.com/adoptium/aqa-tests/pull/4189 just enables some of the tests which were disabled before we found the reason of unexpected exit. Without https://github.com/adoptium/aqa-tests/pull/4119, the tests are still killed by OOM killer.
When running
jdk_vector_0
test, JIT uses too much memory for compiling some methods. For example, the scratch memory (1.5GB) is used up when compilingByte64VectorTests.divByte64VectorTestsMasked(Ljava/util/function/IntFunction;Ljava/util/function/IntFunction;Ljava/util/function/IntFunction;)V
. https://github.com/ibmruntimes/openj9-openjdk-jdk19/blob/110e1e7808efdb0cdd180dfb12a22843777f3d3c/test/jdk/jdk/incubator/vector/Byte64VectorTests.java#L1723-L1742This occurs even when VectorAPIExpansion is disabled (actually, the compilation failed before the optimization phase reaches VectorAPIExpansion). I observed this behavior both on x86 and aarch64.