public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "michaeljclark at mac dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/82261] x86: missing peephole for SHLD / SHRD Date: Mon, 18 May 2020 20:39:20 +0000 [thread overview] Message-ID: <bug-82261-4-BfqYSS8NGL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-82261-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82261 Michael Clark <michaeljclark at mac dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michaeljclark at mac dot com --- Comment #2 from Michael Clark <michaeljclark at mac dot com> --- Just refreshing this issue. I found it while testing some code-gen on Godbolt: - https://godbolt.org/z/uXGxZ9 I noticed that Haswell code-gen uses SHRX/SHLX, but I think -Os and pre-Haswell would benefit from this peephole if it is not complex to add. Noting that Clang prefers SHLD / SHRD over the SHRX+SHLX pair no matter the -march flavor.
next parent reply other threads:[~2020-05-18 20:39 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-82261-4@http.gcc.gnu.org/bugzilla/> 2020-05-18 20:39 ` michaeljclark at mac dot com [this message] 2020-05-19 10:45 ` ubizjak at gmail dot com 2022-04-09 7:00 ` peter at cordes dot ca
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-82261-4-BfqYSS8NGL@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).