From: Andrew Senkevich <andrew.n.senkevich@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] [BZ #19776]: X86-64: Remove previous default/SSE2/AVX2 memcpy/memmove
Date: Fri, 15 Apr 2016 19:04:00 -0000 [thread overview]
Message-ID: <CAMXFM3vZvDBctjmN+8+i8GVywTmV3vCbHuDhQEp1ny41oiAPYw@mail.gmail.com> (raw)
> On Fri, Apr 1, 2016 at 12:38 PM, H.J. Lu <hongjiu.lu@intel.com> wrote:
> Here is the updated patch against master. The current memcpy performance data is at
> https://sourceware.org/bugzilla/attachment.cgi?id=9184
> The current memmove performance data is at
> https://sourceware.org/bugzilla/attachment.cgi?id=9185
> Any comments, feedbacks, objections?
What about performance data on tests with graphics?
There are several use cases, and it could show more helpful information..
--
WBR,
Andrew
next reply other threads:[~2016-04-15 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 19:04 Andrew Senkevich [this message]
2016-04-15 19:06 ` H.J. Lu
2016-05-24 16:54 ` Andrew Senkevich
2016-05-24 17:26 ` H.J. Lu
2016-06-08 20:38 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2016-04-01 19:39 H.J. Lu
2016-04-15 16:29 ` H.J. Lu
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=CAMXFM3vZvDBctjmN+8+i8GVywTmV3vCbHuDhQEp1ny41oiAPYw@mail.gmail.com \
--to=andrew.n.senkevich@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
/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).