public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luc.vanoostenryck at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100028] New: arm64 failure to generate bfxil Date: Sun, 11 Apr 2021 01:44:22 +0000 [thread overview] Message-ID: <bug-100028-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100028 Bug ID: 100028 Summary: arm64 failure to generate bfxil Product: gcc Version: 10.2.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: luc.vanoostenryck at gmail dot com Target Milestone: --- Target: aarch64 Created attachment 50555 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50555&action=edit should generate bfxil but doesn't The attached code reproduced here: #define W 3 #define L 11 int bfxil(int d, int s) { int wmask = (1 << W) - 1; return (d & ~wmask) | ((s >> L) & wmask); } Should return: bfxil: bfxil w0, w1, 11, 3 ret but instead returns: bfxil: ubfx x1, x1, 11, 3 and w0, w0, -8 orr w0, w1, w0 ret The problem is still present in trunk, was also present in 9.3 but wasn't in GCC 8.2 (see https://gcc.godbolt.org/z/E6z31hr9r ).
next reply other threads:[~2021-04-11 1:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-11 1:44 luc.vanoostenryck at gmail dot com [this message] 2021-04-11 2:27 ` [Bug target/100028] [9/10/11 Regression] " pinskia at gcc dot gnu.org 2021-04-12 8:28 ` rguenth at gcc dot gnu.org 2021-04-12 10:59 ` jakub at gcc dot gnu.org 2021-04-12 14:08 ` jakub at gcc dot gnu.org 2021-04-12 15:57 ` jakub at gcc dot gnu.org 2021-04-12 19:53 ` luc.vanoostenryck at gmail dot com 2021-04-13 10:44 ` cvs-commit at gcc dot gnu.org 2021-04-13 10:44 ` [Bug target/100028] [9/10 " jakub at gcc dot gnu.org 2021-04-16 3:42 ` luc.vanoostenryck at gmail dot com 2021-06-01 8:20 ` rguenth at gcc dot gnu.org 2022-05-27 9:44 ` [Bug target/100028] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:44 ` jakub at gcc dot gnu.org 2023-07-07 9:33 ` rguenth 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-100028-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).