This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] aarch64: Optimized implementation of memmove for Qualcomm Falkor
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: Siddhesh Poyarekar <siddhesh at sourceware dot org>, libc-alpha at sourceware dot org
- Cc: nd at arm dot com
- Date: Wed, 04 Oct 2017 15:01:00 +0100
- Subject: Re: [PATCH] aarch64: Optimized implementation of memmove for Qualcomm Falkor
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Szabolcs dot Nagy at arm dot com;
- Nodisclaimer: True
- References: <1505834450-21548-1-git-send-email-siddhesh@sourceware.org>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 19/09/17 16:20, Siddhesh Poyarekar wrote:
> This is an optimized memmove implementation for the Qualcomm Falkor
> processor core. Due to the way the falkor memcpy needs to be written,
> code cannot be easily shared between memmove and memcpy like in case
> of other aarch64 memcpy implementations due to which this routine is
> separate. The underlying principle is the same as that of memcpy
> where it tries to use registers with the same lower 4 bits for
> fetching the same stream, thus optimizing hardware prefetcher
> performance.
>
i think adding a falkor specific memmove is ok,
can you expand on why is it difficult to share code
between memcpy and memmove?