JDK-8162376 : TestSHA512Intrinsics.java failed with Unexpected count of intrinsic _sha5_implCompress is expected
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • CPU: sparc
  • Submitted: 2016-07-22
  • Updated: 2016-08-11
  • Resolved: 2016-07-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b131Fixed
Related Reports
Relates :  
Description
positive_512.log negative_384.log negative_512.log
result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Unexpected count of intrinsic _sha5_implCompress is expected:true, matched: 0, suspected: 2


test result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Unexpected count of intrinsic _sha5_implCompress is expected:true, matched: 0, suspected: 2
Comments
I've investigated a bit more. JDK-8071652 in fact introduced another problem which manifests in a same way. CompileOnly command parameter in test has wrong class... SHA-512 and SHA-384 requires SHA5 provider instead of SHA2. I'll fix this testbug.
22-07-2016

Okay, interesting that no one filed a bug for it yet. Removing integration_blocker label.
22-07-2016

Probably caused by JDK-8071652.
22-07-2016