This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Use memcpy in memmove when possible


On 3/11/2012, at 1:58 PM, Maxim Kuvyrkov wrote:

> On 3/11/2012, at 5:18 AM, 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 been postponing this patch till the new MIPS memcpy is checked in (it is in now).  I'm retesting the patch on MIPS to make sure new memcpy can be used in memmove.
> 
> Dave,
> Carlos,
> 
> If testing is successful, is it still OK to check in the patch?  The patch was approved a while ago, and it affects only MIPS (and TileGX, once Chris checks in his patch).

Ping?

Testing was successful.  Any objections to check in the patch to use memcpy in memmove when safe to do so?

Thank you,

--
Maxim Kuvyrkov
CodeSourcery / Mentor Graphics


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]