Re: BLAKE3 hash redux
| From: | Tim Düsterhus | Date: | Fri, 24 Jan 2025 22:31:28 +0000 |
| Subject: | Re: BLAKE3 hash redux | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-126223@lists.php.net to get a copy of this message | ||
Hi
Am 2025-01-24 22:37, schrieb Hans Henrik Bergan:
BLAKE3 keeping up with dedicated SHA CPU instructions (i.e SHA-NI) is impressive.I would assume that that's the AVX2 implementation (my CPU can't AVX512), which makes it less impressive.
ARM is getting more and more common, and I don't think ARM has SHA instructions (yet?) tho.The ARM architecture has them, but PHP does not yet make use of them. This is mainly due to me being unable to test the integration, due to lacking an appropriate system. libcperciva where I've taken the SHA-NI implementation from also includes the ARM implementation and I checked with the author regarding the necessary attribution as part of the x64 SHA-NI PR: https://github.com/php/php-src/pull/15152#issuecomment-2256476578.
Yes. Ideally mention above that it requires a "2/3 majority" (as with any other RFC, but good to spell it out explicitly). Best regards Tim DüsterhusAs for the RFC itself: I suggest to already add the (closed) voting doodle to the proposed voting choices section. The way the section is currently worded doesn't make sense, because it implies two distinct votes.like this I guess: