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 target/108840] New: Aarch64 doesn't optimize away shift counter masking Date: Fri, 17 Feb 2023 17:59:00 +0000 [thread overview] Message-ID: <bug-108840-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108840 Bug ID: 108840 Summary: Aarch64 doesn't optimize away shift counter masking Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- As mentioned in https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612214.html aarch64 doesn't optimize away and instructions masking shift count if there is more than one shift with the same count. Consider -O2 -fno-tree-vectorize: int foo (int x, int y) { return x << (y & 31); } void bar (int x[3], int y) { x[0] <<= (y & 31); x[1] <<= (y & 31); x[2] <<= (y & 31); } void baz (int x[3], int y) { y &= 31; x[0] <<= y; x[1] <<= y; x[2] <<= y; } void corge (int, int, int); void qux (int x, int y, int z, int n) { n &= 31; corge (x << n, y << n, z >> n); } foo is optimized correctly, combine matches the shift with masking, but in the rest of cases due to costs the desirable combination is rejected. Shift with embedded masking of the count should have rtx_cost the same as normal shift when it is actually under the hood the shift itself.
next reply other threads:[~2023-02-17 17:59 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-17 17:59 jakub at gcc dot gnu.org [this message] 2023-02-17 18:08 ` [Bug target/108840] " pinskia at gcc dot gnu.org 2023-02-21 12:24 ` ktkachov at gcc dot gnu.org 2023-02-24 15:37 ` ktkachov at gcc dot gnu.org 2023-04-19 8:35 ` cvs-commit at gcc dot gnu.org 2023-04-19 8:37 ` ktkachov 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-108840-4@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).