-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 12
-
b07
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8212101 | 11.0.2 | Vladimir Kozlov | P4 | Resolved | Fixed | b01 |
Recently new test was added compiler/intrinsics/base64/TestBase64.java takes long time to run on machines which does not have avx512.
It also has loop with 1000000 iterations to make sure to trigger compilation.
An other similar test is compiler/codegen/aes/TestAESMain.java
Both these test show up as longest running test on some hardware.
First, we should not run these test if intrinsic is not generated (CPU does not support) and you don't need so many iterations to compile code. We should use WB interface to check intrinsics flags and check that method is compiled after warmup instead of doing million iterations.
It also has loop with 1000000 iterations to make sure to trigger compilation.
An other similar test is compiler/codegen/aes/TestAESMain.java
Both these test show up as longest running test on some hardware.
First, we should not run these test if intrinsic is not generated (CPU does not support) and you don't need so many iterations to compile code. We should use WB interface to check intrinsics flags and check that method is compiled after warmup instead of doing million iterations.
- backported by
-
JDK-8212101 Some intrinsic tests take long time to run
-
- Resolved
-
- duplicates
-
JDK-8208124 [TESTBUG] test/hotspot/jtreg/compiler/intrinsics/base64/TestBase64.java fails on some systems
-
- Closed
-
- relates to
-
JDK-8212204 [TESTBUG] test/hotspot/jtreg/compiler/intrinsics/base64/TestBase64.java fails
-
- Resolved
-