RFR: 8293484: AArch64: TestUseSHA512IntrinsicsOptionOnSupportedCPU.java fails on CPU with SHA512 feature support

[Hao Sun]

On Tue, 11 Nov 2025 07:16:18 GMT, Ramkumar Sunderbabu <rsunderbabu at openjdk.org> wrote:

>> Hi, I suppose the failure may occur if we run this test case on CPU **with** SHA512 feature, but **disabling** SHA512Intrinsics.
>> 
>> As **@requires vm.flagless** is set in this jtreg case, if we specify `-XX:-UseSHA512Intrinsics`, this test case is not tested actually. Here shows the log in my machine.
>> 
>> 
>> $ make test TEST=test/hotspot/jtreg/compiler/intrinsics/sha/cli/TestUseSHA512IntrinsicsOptionOnSupportedCPU.java JTREG="VM_OPTIONS=-XX:-UseSHA512Intrinsics"
>> Building target 'test' in configuration '/tmp/local-build-fastdebug'
>> Running tests using JTREG control variable 'VM_OPTIONS=-XX:-UseSHA512Intrinsics'
>> Test selection 'test/hotspot/jtreg/compiler/intrinsics/sha/cli/TestUseSHA512IntrinsicsOptionOnSupportedCPU.java', will run:
>> * jtreg:test/hotspot/jtreg/compiler/intrinsics/sha/cli/TestUseSHA512IntrinsicsOptionOnSupportedCPU.java
>> Clean up dirs for jtreg_test_hotspot_jtreg_compiler_intrinsics_sha_cli_TestUseSHA512IntrinsicsOptionOnSupportedCPU_java
>> 
>> Running test 'jtreg:test/hotspot/jtreg/compiler/intrinsics/sha/cli/TestUseSHA512IntrinsicsOptionOnSupportedCPU.java'
>> Test results: no tests selected
>> Report written to /tmp/local-build-fastdebug/test-results/jtreg_test_hotspot_jtreg_compiler_intrinsics_sha_cli_TestUseSHA512IntrinsicsOptionOnSupportedCPU_java/html/report.html
>> Results written to /tmp/local-build-fastdebug/test-support/jtreg_test_hotspot_jtreg_compiler_intrinsics_sha_cli_TestUseSHA512IntrinsicsOptionOnSupportedCPU_java
>> Finished running test 'jtreg:test/hotspot/jtreg/compiler/intrinsics/sha/cli/TestUseSHA512IntrinsicsOptionOnSupportedCPU.java'
>> Test report is stored in /tmp/local-build-fastdebug/test-results/jtreg_test_hotspot_jtreg_compiler_intrinsics_sha_cli_TestUseSHA512IntrinsicsOptionOnSupportedCPU_java
>> 
>> ==============================
>> Test summary
>> ==============================
>>    TEST                                              TOTAL  PASS  FAIL ERROR  SKIP   
>>    jtreg:test/hotspot/jtreg/compiler/intrinsics/sha/cli/TestUseSHA512IntrinsicsOptionOnSupportedCPU.java
>>                                                          0     0     0     0     0   
>> ==============================
>> TEST SUCCESS
>> 
>> 
>> If so, I don't think it's a bug.
>> Is there anything I misunderstood?
>
> @shqking -XX:-UseSHA512Intrinsics is not the only case of disabling SHA512 instrinsics. Please have a look at your comment https://bugs.openjdk.org/browse/JDK-8293484?focusedId=14532743&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14532743
> Intrinsics was disabled due to lack of test hardware. Please refer @snazarkin comment too. https://bugs.openjdk.org/browse/JDK-8293484?focusedId=14522406&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14522406
> 
> I have come across instances where the support was temporarily disabled due to performance issue or reliability issue.
> Relying on the CPU feature is not a bug per se. But it makes test code maintenance a tad bit difficult.
> I have discussed this in detail under PR description.

Hi @rsunderbabu, thanks for your helpful information.

Another question: can we remove the requirement to run the test case `TestUseSHA512IntrinsicsOptionOnSupportedCPU.java`? I.e., can we remove the following `requires` statement?


 * @requires os.arch!="x86" & os.arch!="i386"

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

PR Comment: https://git.openjdk.org/jdk/pull/28053#issuecomment-3522781500