You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Has anyone run the sha3 test lately?
I've used my own test file, compiled with llvm 18.1.7, using a different build system and running on whisper ISS,
and when linking with the reference version of the sha3 library, I get a different hash compared to online hash tools and python's hashlib.
When I link with the zscrypto_rv64 version, I do get the same hash compared to other tools.
Also, I wonder how the rv64-zscrypto.conf configuration is different rv64-baseline.conf except for the -D__ZSCRYPTO=1 definition.
I guess that file was not updated in 5 years, so it will not work with a newer toolchain, as I don't see the Zk extensions getting added to the -march= anywhere.
Anyhow, did someone run the sha3 test recently and did it pass?
The text was updated successfully, but these errors were encountered:
Has anyone run the sha3 test lately?
I've used my own test file, compiled with llvm 18.1.7, using a different build system and running on whisper ISS,
and when linking with the reference version of the sha3 library, I get a different hash compared to online hash tools and python's hashlib.
When I link with the zscrypto_rv64 version, I do get the same hash compared to other tools.
Also, I wonder how the
rv64-zscrypto.conf
configuration is differentrv64-baseline.conf
except for the-D__ZSCRYPTO=1
definition.I guess that file was not updated in 5 years, so it will not work with a newer toolchain, as I don't see the
Zk
extensions getting added to the-march=
anywhere.Anyhow, did someone run the sha3 test recently and did it pass?
The text was updated successfully, but these errors were encountered: