From: Steve Ellcey <sellcey@cavium.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
libc-alpha <libc-alpha@sourceware.org>
Cc: nd@arm.com
Subject: Re: Ping: [Patch] aarch64: Thunderx specific memcpy and memmove
Date: Thu, 18 May 2017 21:48:00 -0000 [thread overview]
Message-ID: <1495144102.2272.59.camel@cavium.com> (raw)
In-Reply-To: <1494366305.9224.26.camel@cavium.com>
On Tue, 2017-05-09 at 14:45 -0700, Steve Ellcey wrote:
>Â
> 2017-05-09  Steve Ellcey  <sellcey@caviumnetworks.com>
>
> * sysdeps/aarch64/memcpy.S (MEMMOVE, MEMCPY): New macros.
> (memmove): Use MEMMOVE for name.
> (memcpy): Use MEMCPY for name.  Change internal labels
> to external labels.
> * sysdeps/aarch64/multiarch/Makefile: New file.
> * sysdeps/aarch64/multiarch/ifunc-impl-list.c: Likewise.
> * sysdeps/aarch64/multiarch/init-arch.h: Likewise.
> * sysdeps/aarch64/multiarch/memcpy.c: Likewise.
> * sysdeps/aarch64/multiarch/memcpy_generic.S: Likewise.
> * sysdeps/aarch64/multiarch/memcpy_thunderx.S: Likewise.
> * sysdeps/aarch64/multiarch/memmove.c: Likewise.
Ping.
Steve Ellcey
sellcey@cavium.com
next prev parent reply other threads:[~2017-05-18 21:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 18:27 Steve Ellcey
2017-05-01 21:20 ` Wainer dos Santos Moschetta
2017-05-03 14:01 ` Szabolcs Nagy
2017-05-09 3:17 ` Siddhesh Poyarekar
2017-05-09 21:45 ` Steve Ellcey
2017-05-18 21:48 ` Steve Ellcey [this message]
2017-05-19 7:41 ` Siddhesh Poyarekar
[not found] ` <DM5PR07MB34662F805C1EDE45882B82F6F5F90@DM5PR07MB3466.namprd07.prod.outlook.com>
2017-05-24 17:04 ` Szabolcs Nagy
2017-05-25 6:42 ` Siddhesh Poyarekar
2017-05-25 16:28 ` Andrew Pinski
2017-05-25 16:43 ` Ramana Radhakrishnan
2017-05-25 17:49 ` Wilco Dijkstra
2017-05-25 19:26 ` Siddhesh Poyarekar
2017-05-25 21:04 ` Ramana Radhakrishnan
2017-05-25 21:12 ` Florian Weimer
2017-05-26 5:42 ` Siddhesh Poyarekar
2017-05-26 5:34 ` Siddhesh Poyarekar
2017-05-26 5:38 ` Andrew Pinski
2017-05-25 16:22 ` Steve Ellcey
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=1495144102.2272.59.camel@cavium.com \
--to=sellcey@cavium.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=siddhesh@gotplt.org \
--cc=szabolcs.nagy@arm.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).