Re: [PATCH] string: Use memcpy() within memmove() when we can

2020-12-10 Thread Patrick DELAUNAY
Hi Tom, On 12/10/20 12:57 PM, Patrick DELAUNAY wrote: From: Tom Rini Sent: mardi 8 décembre 2020 17:11 On Wed, Nov 25, 2020 at 01:07:43PM +0100, Rasmus Villemoes wrote: On 25/11/2020 12.26, Patrick Delaunay wrote: A common use of memmove() can be handled by memcpy(). Also memcpy() includes a

Re: [PATCH] string: Use memcpy() within memmove() when we can

2020-12-08 Thread Tom Rini
On Wed, Nov 25, 2020 at 01:07:43PM +0100, Rasmus Villemoes wrote: > On 25/11/2020 12.26, Patrick Delaunay wrote: > > A common use of memmove() can be handled by memcpy(). Also memcpy() > > includes an optimization for large sizes: it copies a word at a time. So > > we can get a speed-up by calling

Re: [PATCH] string: Use memcpy() within memmove() when we can

2020-11-25 Thread Rasmus Villemoes
On 25/11/2020 12.26, Patrick Delaunay wrote: > A common use of memmove() can be handled by memcpy(). Also memcpy() > includes an optimization for large sizes: it copies a word at a time. So > we can get a speed-up by calling memcpy() to handle our move in this case. > > Update memmove() to call al

[PATCH] string: Use memcpy() within memmove() when we can

2020-11-25 Thread Patrick Delaunay
A common use of memmove() can be handled by memcpy(). Also memcpy() includes an optimization for large sizes: it copies a word at a time. So we can get a speed-up by calling memcpy() to handle our move in this case. Update memmove() to call also memcpy() if the source don't overlap the destination