From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Steve Ellcey <sellcey@mips.com>
Cc: <libc-ports@sourceware.org>
Subject: Re: [patch, mips, memmove] Remove memmove's use of memcpy on MIPS
Date: Fri, 25 Jan 2013 23:15:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1301252314220.31629@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1359149324.11963.183.camel@ubuntu-sellcey>
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
next prev parent reply other threads:[~2013-01-25 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 18:17 Steve Ellcey
2013-01-25 18:55 ` Chris Metcalf
2013-01-25 19:29 ` Steve Ellcey
2013-01-25 20:16 ` Joseph S. Myers
2013-01-25 21:29 ` Steve Ellcey
2013-01-25 23:15 ` Joseph S. Myers [this message]
2013-01-26 2:09 ` Maxim Kuvyrkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.1301252314220.31629@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=sellcey@mips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).