SHA-1 with collision detection doesn't have to be so slow. How a code generator that moves the checks to SIMD can narrow the gap to plain SHA-1 to ~20–30%.
10 comments
What would you do better?
Also, the author didn't say that there were no other tests. They just said that they use fuzz + property tests a fair bit.
Maybe an LLM did the search for what expressions to put in the blocks vs tail of the vectorized collision detection, but that seems like a good place to use an LLM as long as all of the expected bit relations are verified as checked properly.
It needs to stop, if people have a factual or actual valid criticism of the facts or claims then by all means, go to town. But Im done with the slop screamers, its a downvote and scorn all the way down for those
Read the full thread on Hacker News →
Related stories
- Lobsters · 86 points · about 1 year ago
- Writing Rust code that's faster than state-of-the-art libraries by asking agents to make the code fasterminimaxir.comLobsters · 5 points · 8 days ago
- Hacker News · 2 points · 9 days ago
- Hacker News · 1 points · 9 days ago
- Hacker News · 8 points · 6 days ago
- Hacker News · 73 points · 8 days ago