This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Use memcpy in memmove when possible
- From: Chris Metcalf <cmetcalf at tilera dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: Roland McGrath <roland at hack dot frob dot com>, Maxim Kuvyrkov<maxim at codesourcery dot com>, GLIBC Devel <libc-alpha at sourceware dot org>
- Date: Tue, 6 Nov 2012 15:07:11 -0500
- Subject: Re: [PATCH] Use memcpy in memmove when possible
- References: <A9D6160A-41F1-48E7-851F-F2D4F7134EB3@codesourcery.com> <20120906195816.6446C2C0BF@topped-with-meat.com> <09E2BC4C-8883-4D8D-84B9-77630075EE89@codesourcery.com> <20120907163239.9224F2C0D0@topped-with-meat.com> <Pine.LNX.4.64.1209071636550.13248@digraph.polyomino.org.uk> <5093F238.1000309@tilera.com>
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