From: Ulrich Drepper <drepper@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: libc patch: update of memcpy et al
Date: Sun, 27 May 2001 06:45:12 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005673@msgid-missing> (raw)
David Mosberger <davidm@hpl.hp.com> writes:
> The patch below bring the performance of memcpy(), memmove(), bcopy(),
> and bzero() up to more reasonable levels. I haven't run this through
> "make check", but I believe the changes to be OK.
The changes seem fine, I ran make check. Thanks. But you were really
naughty and edited the patch. Tss, tss, tss, don't do that, it's so
easy to do it wrong just as in this case.
Also, there is no need to introduce __memmove. __-protected functions
are only necessary to prevent namespace problems. Since memmove is
defined in the most basic standards there is no problem at all.
Thanks,
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
reply other threads:[~2001-05-27 6:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590693005673@msgid-missing \
--to=drepper@redhat.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox