This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
RE: [PATCH] Improve strncpy performance further
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "Wilco Dijkstra" <wdijkstr at arm dot com>
- Cc: <libc-alpha at sourceware dot org>
- Date: Fri, 9 Jan 2015 11:16:32 -0800 (PST)
- Subject: RE: [PATCH] Improve strncpy performance further
- Authentication-results: sourceware.org; auth=none
- References: <001801d02b72$6ce0c3c0$46a24b40$ at com> <20150108185812 dot 285782C3BF6 at topped-with-meat dot com> <001901d02c0d$43cf9920$cb6ecb60$ at com>
> Btw while on the subject on namespaces, is bcopy correctly defined?
> After a lot of complex inclusion and defines, it ultimately does:
>
> void
> bcopy ()
> {
> ...
> }
I'm not sure what kind of correctness you have in mind. bcopy is the only
name under which that function needs to be defined. If it's in the same
file as a standard function (presumably memmove) then it needs to be
defined as weak. No other code anywhere in libc should call bcopy (we'd
use memmove or memcpy instead), so it doesn't need to have an __ name.