[PATCH] x86_64: Implement AVX2 version of strlcpy/wcslcpy function
Paul Eggert
eggert@cs.ucla.edu
Mon Jul 3 21:14:08 GMT 2023
On 2023-07-03 11:40, Noah Goldstein wrote:
> Think we should look into dropping optimized strcpy/wcscpy family
> in general?
For wcscpy yes. Who uses wcscpy? Optimizing it is a worthless time sink.
strcpy optimization might be worth keeping, as it's used so much more.
Measurements of real programs would help decide. In the meantime inertia
suggests that when in doubt, leave it alone.
For strlcpy it's an easy call: don't optimize unless realistic
benchmarks show it's a win.
More information about the Libc-alpha
mailing list