It seems SHA256AutoDetect() was not being called in benchmarks, making the numbers only reflect the naive implementation. Fix this by calling it in bench_bitcoin's setup.
This is a backport of core#19214
Differential D10004
Call SHA256AutoDetect in benchmark setup PiRK on Sep 1 2021, 09:26. Authored by Tags None Subscribers None
Details
This is a backport of core#19214 ninja bench-bitcoin I don't see a significant difference in the SHA256 becnhmarks before or
Diff Detail
|