public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "skpgkp2 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/24872] __memmove_avx_unaligned_erms() performs significantly much slower than __memcpy_ssse3()
Date: Thu, 25 Mar 2021 16:59:02 +0000	[thread overview]
Message-ID: <bug-24872-131-joBz36DY21@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24872-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24872

--- Comment #9 from Sunil Pandey <skpgkp2 at gmail dot com> ---
Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz

$ time ./a.out

real    0m29.613s
user    0m29.585s
sys     0m0.003s

$ time
GLIBC_TUNABLES=glibc.cpu.hwcaps=-AVX_Fast_Unaligned_Load,-Fast_Unaligned_Copy
./a.out

real    0m29.651s
user    0m29.622s
sys     0m0.004s

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-03-25 16:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24872-131@http.sourceware.org/bugzilla/>
2020-05-30 15:30 ` jan at jki dot io
2021-03-24 23:46 ` hjl.tools at gmail dot com
2021-03-25  0:05 ` hjl.tools at gmail dot com
2021-03-25  2:42 ` skpgkp2 at gmail dot com
2021-03-25  3:00 ` skpgkp2 at gmail dot com
2021-03-25  5:53 ` skpgkp2 at gmail dot com
2021-03-25 13:04 ` hjl.tools at gmail dot com
2021-03-25 13:05 ` hjl.tools at gmail dot com
2021-03-25 13:16 ` skpgkp2 at gmail dot com
2021-03-25 16:28 ` skpgkp2 at gmail dot com
2021-03-25 16:59 ` skpgkp2 at gmail dot com [this message]
2021-05-29  5:54 ` gouhaojake at 163 dot com
2021-05-30  1:24 ` gouhaojake at 163 dot com
2021-05-30  1:40 ` hjl.tools at gmail dot com
2021-05-30  1:41 ` hjl.tools at gmail dot com
2021-05-30  5:07 ` gouhaojake at 163 dot com

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=bug-24872-131-joBz36DY21@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).