The ups and downs of strlcpy()

Posted Jul 20, 2012 2:45 UTC (Fri) by Ben_P (guest, #74247)
In reply to: The ups and downs of strlcpy() by nix
Parent article: The ups and downs of strlcpy()

Hmm, thanks. Do you happen to know if SPARC, Niagara 2's specifically, give strcpy and strncpy similar assistance?

The ups and downs of strlcpy()

Posted Jul 20, 2012 12:54 UTC (Fri) by nix (subscriber, #2304) [Link] (1 responses)

glibc/sysdeps/sparc/sparc32/sparcv9/str*cpy.S redirect to the corresponding files in glibc/sysdeps/sparc/sparc64/, which use the 64-bit SPARC instruction set but do *not* use VIS or other extensions yet. There are VIS-using implementations of memcpy() and memset() in glibc/sysdeps/sparc/sparc64/multiarch/, but nothing similar for string instructions so far. (This is all in glibc trunk.)

Obviously the GCC builtins for strcpy() et al still work.

The ups and downs of strlcpy()

Posted Jul 23, 2012 17:58 UTC (Mon) by BenHutchings (subscriber, #37955) [Link]

David Miller was doing some work on string optimisations on SPARC and more generally a while back; see the March and April 2010 entries in <http://vger.kernel.org/~davem/cgi-bin/blog.cgi/index.html>.