public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105825] [13 Regression] ICE: in extract_insn, at recog.cc:2791 (unrecognizable insn) with -mavx Date: Sat, 04 Jun 2022 08:37:48 +0000 [thread overview] Message-ID: <bug-105825-4-wWKQnfBDzs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105825-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105825 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:53718316afa45eb0d1c236fbbf2fc0959b08510f commit r13-989-g53718316afa45eb0d1c236fbbf2fc0959b08510f Author: Jakub Jelinek <jakub@redhat.com> Date: Sat Jun 4 10:36:24 2022 +0200 i386: Fix up *_doubleword_mask [PR105825] My PR105778 patch apparently broke the following testcase. If the mask has the top relevant bit clear (i.e. we know we are shifting by 0 to wordsize bits - 1) but doesn't have all the bits below it set, we emit andsi3 before the shift sequence. When the pattern had :SI for that operand, that was just fine, but now that it can be also HImode or for -m64 DImode, we either can use a lowpart or paradoxical subreg to SImode as the following patch, or we use a HImode or DImode AND. This patch does the latter. 2022-06-04 Jakub Jelinek <jakub@redhat.com> PR target/105825 * config/i386/i386.md (*ashl<dwi>3_doubleword_mask, *<insn><dwi>3_doubleword_mask): If top bit of mask is clear, but lower bits of mask aren't all set, use operands[2] mode for the AND operation instead of always SImode. * gcc.dg/pr105825.c: New test.
next prev parent reply other threads:[~2022-06-04 8:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-02 19:14 [Bug target/105825] New: " zsojka at seznam dot cz 2022-06-03 7:40 ` [Bug target/105825] " jakub at gcc dot gnu.org 2022-06-03 10:13 ` jakub at gcc dot gnu.org 2022-06-04 8:37 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-19 10:16 ` 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-105825-4-wWKQnfBDzs@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).