public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wdijkstr at arm dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug string/28216] interleaving load/store instructions in memcpy for aarch64 Date: Thu, 21 Apr 2022 14:54:35 +0000 [thread overview] Message-ID: <bug-28216-131-2uen8dA0c4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28216-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28216 Wilco <wdijkstr at arm dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wdijkstr at arm dot com --- Comment #2 from Wilco <wdijkstr at arm dot com> --- Memcpy shares code with memmove for sizes up to 128 bytes, so it is essential to do all loads before any store. Finegrained interleaving of loads/stores isn't needed on out-of-order cores - all you want to avoid is extremes like doing 32 loads and then 32 stores. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-04-21 14:54 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-10 4:28 [Bug string/28216] New: " wangxuszcn at foxmail dot com 2021-08-10 8:03 ` [Bug string/28216] " wangxuszcn at foxmail dot com 2022-04-21 14:54 ` wdijkstr at arm dot com [this message]
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-28216-131-2uen8dA0c4@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: linkBe 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).