[PATCH] Use memcpy in memmove when possible

[Chris Metcalf]

On 11/2/2012 12:18 PM, Chris Metcalf wrote:
> On 9/7/2012 12:37 PM, Joseph S. Myers wrote:
>> On Fri, 7 Sep 2012, Roland McGrath wrote:
>>
>>> The generic part of the change looks fine to me.  But it should only go in
>>> if the mips change is approved so the macro has a user.
>> The MIPS change is OK if it has been tested for both 32-bit and 64-bit 
>> ABIs.
> Ping!
>
> We have been carrying a variant of this exact patch in the tilegx
> architecture recently (since we only recently fixed up our memcpy to be
> safe for forward overlapping memmove).  Maxim, are you planning to commit
> this prior to the 2.17 code freeze?  I'd like to see the tilegx memmove
> take advantage of this.

I've committed the change to make tilegx forward memcpy safe for memmove,
so I'm hopeful Maxim's memmove change can get in for 2.17.

-- 
Chris Metcalf, Tilera Corp.
http://www.tilera.com