-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing sha2 benchmarks to refer to the faster Hacl_SHA2_Streaming versions #362
base: main
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 4252472757
💛 - Coveralls |
|
||
template<class... Args> | ||
void | ||
HACL_Sha2_new_oneshot(benchmark::State& state, Args&&... args) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this function isn't used?
Please remove or use.
@@ -159,7 +174,7 @@ BENCHMARK_CAPTURE(HACL_Sha2_oneshot, | |||
sha2_224, | |||
HACL_HASH_SHA2_224_DIGEST_LENGTH, | |||
expected_digest_sha2_224, | |||
Hacl_Hash_SHA2_hash_224) | |||
Hacl_Streaming_SHA2_sha224) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes the benchmark pretend like the oneshot function exposed by the library have this performance. Which they don't
I agree that this should be used but a few things need to happen as well
- remove the slow API
- update the documentation to point consumers to the right API
I'm fine with doing this in follow-ups. But it either needs to be filed as follow-ups to tackle after this (maybe @duesee or @pnmadelaine can take care of this), or done here.
No description provided.