From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10393 invoked by alias); 25 Jan 2013 23:15:39 -0000 Received: (qmail 10374 invoked by uid 22791); 25 Jan 2013 23:15:34 -0000 X-SWARE-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,TW_CP X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 25 Jan 2013 23:15:04 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1TysU9-0003AQ-Un from joseph_myers@mentor.com ; Fri, 25 Jan 2013 15:15:01 -0800 Received: from SVR-IES-FEM-01.mgc.mentorg.com ([137.202.0.104]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 25 Jan 2013 15:15:01 -0800 Received: from digraph.polyomino.org.uk (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.1.289.1; Fri, 25 Jan 2013 23:14:59 +0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.76) (envelope-from ) id 1TysU6-0008Hr-Fm; Fri, 25 Jan 2013 23:14:58 +0000 Date: Fri, 25 Jan 2013 23:15:00 -0000 From: "Joseph S. Myers" To: Steve Ellcey CC: Subject: Re: [patch, mips, memmove] Remove memmove's use of memcpy on MIPS In-Reply-To: <1359149324.11963.183.camel@ubuntu-sellcey> Message-ID: References: <8eea9547-6de4-482b-833c-f552df9283d4@EXCHHUB01.MIPS.com> <1359149324.11963.183.camel@ubuntu-sellcey> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org X-SW-Source: 2013-01/txt/msg00061.txt.bz2 On Fri, 25 Jan 2013, Steve Ellcey wrote: > I am hoping to improve memcpy at some point so that it will be safe to > use memcpy in memmove again. Given that, do you think I should still > just remove the MIPS memmove.c and recreate it later when needed or > would it make sense to keep it so I can just set the macro when it is > safe to do so. It should be removed, as currently not useful, then recreated if and when such a file is useful again. -- Joseph S. Myers joseph@codesourcery.com