public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Pawar, Amit" <Amit.Pawar@amd.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: RE: [PATCH x86_64] Update memcpy, mempcpy and memmove selection order for Excavator CPU BZ #19583
Date: Fri, 18 Mar 2016 15:19:00 -0000	[thread overview]
Message-ID: <SN1PR12MB0733C372AE1AFC950CFBBF44978C0@SN1PR12MB0733.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAMe9rOr11s9j7i4Gk2yozXY-MWJLKpFXCKkFqoLW553tyJ4LZg@mail.gmail.com>

>One question.  If  you don't want __memcpy_avx_unaligned, why do you set AVX_Fast_Unaligned_Load?
Any idea whether currently any other string and memory functions are under implementation based on this? If not then let me just verify it. 

Also this feature is enabled in generic code. To disable it, need to change after this.

--Amit Pawar

  reply	other threads:[~2016-03-18 15:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 10:52 Pawar, Amit
2016-03-17 11:53 ` H.J. Lu
2016-03-17 14:16   ` Pawar, Amit
2016-03-17 14:46     ` H.J. Lu
2016-03-18 11:43       ` Pawar, Amit
2016-03-18 11:51         ` H.J. Lu
2016-03-18 12:25           ` Pawar, Amit
2016-03-18 12:34             ` H.J. Lu
2016-03-18 13:22               ` Pawar, Amit
2016-03-18 13:51                 ` H.J. Lu
2016-03-18 13:55                   ` Adhemerval Zanella
2016-03-18 14:43                     ` H.J. Lu
2016-03-18 14:45                   ` H.J. Lu
2016-03-18 15:19                     ` Pawar, Amit [this message]
2016-03-18 15:24                       ` H.J. Lu
2016-03-22 11:08                         ` Pawar, Amit
2016-03-22 14:50                           ` H.J. Lu
2016-03-22 14:57                             ` Pawar, Amit
2016-03-22 15:03                               ` H.J. Lu
2016-03-23 10:12                                 ` Pawar, Amit
2016-03-23 17:59                                   ` H.J. Lu
2016-03-28  7:43                                     ` Pawar, Amit
2016-03-28 12:12                                       ` 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=SN1PR12MB0733C372AE1AFC950CFBBF44978C0@SN1PR12MB0733.namprd12.prod.outlook.com \
    --to=amit.pawar@amd.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).