From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Will Newton <will.newton@linaro.org>
Cc: <libc-ports@sourceware.org>, <patches@linaro.org>
Subject: Re: [PATCH, v6] ARM: Add Cortex-A15 optimized NEON and VFP memcpy routines, with IFUNC.
Date: Fri, 03 May 2013 20:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1305032015060.30366@digraph.polyomino.org.uk> (raw)
In-Reply-To: <518171B2.5020504@linaro.org>
On Wed, 1 May 2013, Will Newton wrote:
> This was tested on armv7l-unknown-linux-gnueabihf. One new testsuite
I think string functions also need big-endian testing (which should be
possible with userspace QEMU - you should be able to run the string tests
that way, though not the whole testsuite). If such testing passes, this
version is OK (though as Roland notes there's scope for further
optimization in the __ARM_NEON__ case).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-05-03 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 19:49 Will Newton
2013-05-03 20:19 ` Joseph S. Myers [this message]
2013-05-03 21:14 ` Will Newton
2013-05-04 13:13 ` Joseph S. Myers
2013-05-08 9:44 ` Will Newton
2013-05-08 12:07 ` Joseph S. Myers
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=Pine.LNX.4.64.1305032015060.30366@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=patches@linaro.org \
--cc=will.newton@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).