[PATCH] aarch64: Optimized implementation of memmove for Qualcomm Falkor

[Siddhesh Poyarekar]

On Wednesday 04 October 2017 07:31 PM, Szabolcs Nagy wrote:
> i think adding a falkor specific memmove is ok,
> can you expand on why is it difficult to share code
> between memcpy and memmove?

The algorithms for memmove and memcpy are quite different, from the copy
loop sizes to prefetching behaviour because of the memmove requirement
to work on overlaps.  Using multiple registers in memmove to expand the
copy look to the memcpy size regresses performance for memmove while
reducing the copy loop size in memcpy regresses memcpy, so it doesn't
make sense to try and unify the implementations.

Siddhesh