public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106323] [Suboptimal] memcmp(s1, s2, n) == 0 expansion on AArch64 compare to llvm Date: Sun, 17 Jul 2022 20:23:15 +0000 [thread overview] Message-ID: <bug-106323-4-5VhvjjOkyF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106323-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106323 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- GCC might be better if the first bytes are in cache but the next bytes are not and then branch is predictable (which it might be). So this is much more complex than just changing this really.
next prev parent reply other threads:[~2022-07-17 20:23 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-16 9:55 [Bug c/106323] New: " zhongyunde at huawei dot com 2022-07-17 20:23 ` pinskia at gcc dot gnu.org [this message] 2022-07-17 20:37 ` [Bug middle-end/106323] " pinskia at gcc dot gnu.org 2022-07-18 7:31 ` wilco at gcc dot gnu.org 2022-12-06 13:03 ` zhongyunde at huawei 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-106323-4-5VhvjjOkyF@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).