public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108941] Error: operand type mismatch for `shr' with binutils master Date: Mon, 27 Feb 2023 11:23:41 +0000 [thread overview] Message-ID: <bug-108941-4-t1CKXSXn5G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108941-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108941 --- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> --- We could file an x86 backend enhancement request based on those comments, int foo (int x, int y) { return x << (y & 31); } int bar (int x, int y) { return x << (32 + y); } int baz (int x, int y) { return x << (-y & 31); } int qux (int x, int y) { return x << (32 - y); } where we optimize away the & 31 masks, but actually not the additions of 32. It actually doesn't change anything on the number of instructions in this case, but bar needs 1 more bytes than equivalent foo and qux even 3 more bytes than equivalent baz.
next prev parent reply other threads:[~2023-02-27 11:23 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-27 9:39 [Bug c/108941] New: " marxin at gcc dot gnu.org 2023-02-27 9:51 ` [Bug c/108941] " jakub at gcc dot gnu.org 2023-02-27 10:00 ` marxin at gcc dot gnu.org 2023-02-27 10:07 ` jakub at gcc dot gnu.org 2023-02-27 10:17 ` jbeulich at suse dot com 2023-02-27 10:33 ` jakub at gcc dot gnu.org 2023-02-27 10:57 ` jbeulich at suse dot com 2023-02-27 11:00 ` jbeulich at suse dot com 2023-02-27 11:02 ` jakub at gcc dot gnu.org 2023-02-27 11:11 ` jbeulich at suse dot com 2023-02-27 11:14 ` jakub at gcc dot gnu.org 2023-02-27 11:17 ` jakub at gcc dot gnu.org 2023-02-27 11:17 ` marxin at gcc dot gnu.org 2023-02-27 11:23 ` jakub at gcc dot gnu.org [this message] 2023-02-28 7:33 ` jbeulich at suse dot com 2023-02-28 7:47 ` jakub at gcc dot gnu.org 2023-02-28 7:59 ` jbeulich at suse dot com 2023-02-28 8:10 ` jakub at gcc dot gnu.org
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-108941-4-t1CKXSXn5G@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).