This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author oconnor663
Recipients Zooko.Wilcox-O'Hearn, christian.heimes, corona10, jstasiak, kmaork, larry, mgorny, oconnor663, xtreak
Date 2022-01-13.02:59:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1642042798.26.0.647025009412.issue39298@roundup.psfhosted.org>
In-reply-to
Content
Yeah by intrinsics I mean stuff like _mm256_add_epi32(). All of that stuff is in these vendored files:

blake3_avx2.c
blake3_avx512.c
blake3_neon.c
blake3_sse2.c
blake3_sse41.c

Also to Michał's question above, I'm not necessarily opposed to publishing something like "blake3-c" on PyPI once things stabilize. Even if we get BLAKE3 into hashlib in 3.11, PyPI modules will be useful to folks running older versions, and not everyone wants to install the Rust toolchain.
History
Date User Action Args
2022-01-13 02:59:58oconnor663setrecipients: + oconnor663, larry, christian.heimes, mgorny, Zooko.Wilcox-O'Hearn, jstasiak, corona10, xtreak, kmaork
2022-01-13 02:59:58oconnor663setmessageid: <1642042798.26.0.647025009412.issue39298@roundup.psfhosted.org>
2022-01-13 02:59:58oconnor663linkissue39298 messages
2022-01-13 02:59:58oconnor663create