From: Will Newton <will.newton@linaro.org>
To: Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
Cc: Richard Henderson <rth@twiddle.net>,
libc-ports@sourceware.org, Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH v2] ARM: Add Cortex-A15 optimized NEON and VFP memcpy routines, with IFUNC.
Date: Thu, 18 Apr 2013 07:54:00 -0000 [thread overview]
Message-ID: <CANu=DmjTT6ydMcvqWZ=M5ckQE9Riqt0k+BCRSrR6hFrkLB0TOA@mail.gmail.com> (raw)
In-Reply-To: <CAAHN_R0cE3LQVH9iEENaS=6Zq2U2E1Fa6SkUyQGYd-z0w7Ki_Q@mail.gmail.com>
On 18 April 2013 08:47, Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com> wrote:
> On 18 April 2013 13:12, Richard Henderson <rth@twiddle.net> wrote:
>> On 2013-04-17 17:53, Will Newton wrote:
>>>>
>>>> From reading the comments of the code v7 is required for NEON, v6 is
>>>
>>> required for VFP and unaligned access is required. The unaligned
>>> access requirement may be a problem on v5 I'm not sure. NB: I did not
>>> write the memcpy code so I have not looked at it in great detail.
>>
>>
>> Neon won't exist before v7, true. But then it ought not be advertized
>> by the hwcap either, so it won't be selected.
>>
>> Anyone got a raspberry pi to benchmark the current and the new here?
>
> I can do the benchmark on my raspberry pi.
Hi Siddesh,
Thanks for the offer, I don't have any armv6 hardware to test with.
The easiest way to test is probably using the cortex-strings package
(as the patch I posted is for armv7).
https://launchpad.net/cortex-strings
"try-this -t memcpy" will benchmark the code I submitted, "try-glibc
-t memcpy" will benchmark the current glibc code.
--
Will Newton
Toolchain Working Group, Linaro
next prev parent reply other threads:[~2013-04-18 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 9:25 Will Newton
2013-04-17 15:40 ` Richard Henderson
2013-04-17 15:53 ` Will Newton
2013-04-18 7:42 ` Richard Henderson
2013-04-18 7:47 ` Siddhesh Poyarekar
2013-04-18 7:54 ` Will Newton [this message]
2013-04-18 8:26 ` Siddhesh Poyarekar
2013-04-18 8:38 ` Will Newton
2013-04-18 17:58 ` Siddhesh Poyarekar
2013-04-22 8:27 ` Will Newton
2013-04-17 17:51 ` Carlos O'Donell
2013-04-18 8:01 ` Will Newton
2013-04-19 21:47 ` Joseph S. Myers
2013-04-22 8:32 ` Will Newton
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='CANu=DmjTT6ydMcvqWZ=M5ckQE9Riqt0k+BCRSrR6hFrkLB0TOA@mail.gmail.com' \
--to=will.newton@linaro.org \
--cc=libc-ports@sourceware.org \
--cc=patches@linaro.org \
--cc=rth@twiddle.net \
--cc=siddhesh.poyarekar@gmail.com \
/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).