public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98681] [8/9/10/11 Regression] aarch64: Invalid ubfiz instruction rejected by assembler Date: Thu, 14 Jan 2021 13:45:33 +0000 [thread overview] Message-ID: <bug-98681-4-nO5eQTo4PG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98681-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98681 ktkachov at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |ktkachov at gcc dot gnu.org Summary|aarch64: Invalid ubfiz |[8/9/10/11 Regression] |instruction rejected by |aarch64: Invalid ubfiz |assembler |instruction rejected by | |assembler Priority|P3 |P2 Last reconfirmed| |2021-01-14 --- Comment #1 from ktkachov at gcc dot gnu.org --- Confirmed. GCC 5 didn't generate the bogus assembly. I suppose the predicate and/or constraint of *andim_ashift<mode>_bfiz needs tightening
next prev parent reply other threads:[~2021-01-14 13:45 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-14 13:31 [Bug target/98681] New: " acoplan at gcc dot gnu.org 2021-01-14 13:31 ` [Bug target/98681] " acoplan at gcc dot gnu.org 2021-01-14 13:45 ` ktkachov at gcc dot gnu.org [this message] 2021-01-14 13:56 ` [Bug target/98681] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org 2021-01-15 2:26 ` pinskia at gcc dot gnu.org 2021-01-22 15:35 ` jakub at gcc dot gnu.org 2021-01-22 15:51 ` jakub at gcc dot gnu.org 2021-01-22 16:37 ` rearnsha at gcc dot gnu.org 2021-01-22 16:47 ` jakub at gcc dot gnu.org 2021-01-22 17:36 ` jakub at gcc dot gnu.org 2021-01-22 17:56 ` jakub at gcc dot gnu.org 2021-01-26 13:50 ` cvs-commit at gcc dot gnu.org 2021-01-26 14:00 ` [Bug target/98681] [8/9/10 " jakub at gcc dot gnu.org 2021-01-29 19:20 ` cvs-commit at gcc dot gnu.org 2021-01-29 19:24 ` [Bug target/98681] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:31 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:50 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:11 ` 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-98681-4-nO5eQTo4PG@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).