Skip to content

Commit dfc295f

Browse files
committed
remove unnecessary info from the code comment
1 parent 597c675 commit dfc295f

File tree

1 file changed

+5
-10
lines changed

1 file changed

+5
-10
lines changed

Python/pystrhex.c

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -26,20 +26,15 @@ _Py_hexlify_scalar(const unsigned char *src, Py_UCS1 *dst, Py_ssize_t len)
2626
native SIMD instructions (SSE2 punpcklbw/punpckhbw on x86-64 [always],
2727
NEON zip1/zip2 on ARM64 [always], & vzip on ARM32 when compiler flags
2828
for the target microarch allow it [try -march=native if running 32-bit
29-
on an rpi3 or later]).
30-
31-
Requirements:
32-
- GCC 12+ or Clang 3.0+ (for __builtin_shufflevector)
33-
- x86-64, ARM64, or ARM32 with NEON
29+
on an RPi3 or later]).
3430
3531
Performance:
36-
- Up to 11x faster on larger data than the scalar code.
3732
- For more common small data it varies between 1.1-3x faster.
33+
- Up to 11x faster on larger data than the scalar code.
3834
39-
Even faster is possible for big data using AVX2 or AVX512 but
40-
that adds complication. Honestly, who really hexes _huge_ data?!
41-
42-
Speeding up the 16-64 byte cases fits nicely with md5 through sha512.
35+
While faster is possible for big data using AVX2 or AVX512, that
36+
adds a ton of complication. Who ever really hexes huge data?
37+
The 16-64 byte boosts align nicely with md5 - sha512 hexdigests.
4338
*/
4439
#ifdef HAVE_BUILTIN_SHUFFLEVECTOR_AND_IT_IS_WORTH_USING
4540

0 commit comments

Comments
 (0)