From: Steve Ellcey <sellcey@mips.com>
To: Maxim Kuvyrkov <maxim@codesourcery.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
<libc-ports@sourceware.org>
Subject: Re: [PATCH] Optimize MIPS memcpy
Date: Wed, 19 Dec 2012 16:59:00 -0000 [thread overview]
Message-ID: <1355936320.31899.7.camel@ubuntu-sellcey> (raw)
In-Reply-To: <EF339445-641A-4A99-B88B-2B64A68206F6@codesourcery.com>
On Wed, 2012-12-19 at 14:51 +1300, Maxim Kuvyrkov wrote:
> Steve,
>
> Would you please add a NEWS entry for improved MIPS memcpy? It's a significant performance improvement, and deserves a note.
>
> Thanks,
>
> --
> Maxim Kuvyrkov
> CodeSourcery / Mentor Graphics
OK, I have added this:
2012-12-19 Steve Ellcey <sellcey@mips.com>
* NEWS: Mention new memcpy for MIPS.
diff --git a/NEWS b/NEWS
index e58fabe..3a15555 100644
--- a/NEWS
+++ b/NEWS
@@ -25,6 +25,8 @@ Version 2.17
14838, 14856, 14863, 14865, 14866, 14868, 14869, 14871, 14872, 14879,
14889, 14893, 14898, 14914.
+* Optimization of memcpy for MIPS.
+
* CVE-2011-4609 svc_run() produces high cpu usage when accept fails with
EMFILE has been fixed (Bugzilla #14889).
next prev parent reply other threads:[~2012-12-19 16:59 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 6:16 Maxim Kuvyrkov
2012-09-01 16:37 ` Joseph S. Myers
2012-09-03 9:12 ` Andrew T Pinski
2012-09-03 17:12 ` Maxim Kuvyrkov
2012-09-04 15:09 ` Steve Ellcey
2012-09-04 15:14 ` Carlos O'Donell
2012-09-04 17:03 ` Steve Ellcey
2012-09-04 17:28 ` Carlos O'Donell
2012-09-05 0:43 ` Maxim Kuvyrkov
2012-09-06 16:25 ` Steve Ellcey
2012-09-06 18:43 ` Roland McGrath
2012-09-06 19:37 ` Steve Ellcey
2012-09-07 21:24 ` Maxim Kuvyrkov
2012-09-11 4:35 ` Maxim Kuvyrkov
2012-09-11 15:18 ` Steve Ellcey
2012-09-20 9:05 ` Maxim Kuvyrkov
2012-09-20 18:38 ` Steve Ellcey
2012-09-28 3:48 ` Maxim Kuvyrkov
2012-10-06 4:43 ` Maxim Kuvyrkov
2012-10-08 17:04 ` Steve Ellcey
2012-10-08 22:31 ` Maxim Kuvyrkov
2012-10-09 20:50 ` Steve Ellcey
2012-10-15 17:49 ` Steve Ellcey
2012-10-15 20:20 ` Andrew Pinski
2012-10-15 20:34 ` Steve Ellcey
2012-10-15 20:42 ` Andrew Pinski
2012-10-15 20:50 ` Andrew Pinski
2012-10-15 21:36 ` Steve Ellcey
2012-10-15 21:47 ` Maxim Kuvyrkov
2012-10-17 17:30 ` Steve Ellcey
2012-10-29 18:00 ` Steve Ellcey
2012-10-29 18:03 ` Maxim Kuvyrkov
2012-10-30 7:16 ` Maxim Kuvyrkov
2012-10-30 7:19 ` Maxim Kuvyrkov
2012-10-30 17:46 ` Steve Ellcey
2012-10-30 21:56 ` Maxim Kuvyrkov
2012-10-30 22:19 ` Steve Ellcey
2012-12-19 1:51 ` Maxim Kuvyrkov
2012-12-19 16:59 ` Steve Ellcey [this message]
2012-10-31 19:27 ` Andreas Jaeger
2012-10-31 20:04 ` Steve Ellcey
2012-10-15 22:10 ` Joseph S. Myers
2012-10-15 21:29 ` Maciej W. Rozycki
2012-10-15 22:05 ` Maxim Kuvyrkov
2012-09-21 18:47 ` Steve Ellcey
2012-09-21 18:57 ` Joseph S. Myers
2012-09-21 20:41 ` [PATCH] Optimize MIPS memcpy (mips glibc test results) Steve Ellcey
2012-09-21 20:49 ` Joseph S. Myers
2012-09-21 20:56 ` Steve Ellcey
2012-09-21 19:12 ` [PATCH] Optimize MIPS memcpy 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=1355936320.31899.7.camel@ubuntu-sellcey \
--to=sellcey@mips.com \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=maxim@codesourcery.com \
--cc=pinskia@gmail.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).