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/105854] ICE: in extract_constrain_insn, at recog.cc:2692 (insn does not satisfy its constraints: sse2_lshrv1ti3) Date: Wed, 08 Jun 2022 03:17:39 +0000 [thread overview] Message-ID: <bug-105854-4-j22pB9aQCB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105854-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105854 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:c45a9752f15bbc37d8efda0e29af5a2bfd53729d commit r12-8462-gc45a9752f15bbc37d8efda0e29af5a2bfd53729d Author: liuhongt <hongtao.liu@intel.com> Date: Mon Jun 6 13:39:19 2022 +0800 Fix insn does not satisfy its constraints: sse2_lshrv1ti3 21114(define_insn_and_split "ssse3_palignrdi" 21115 [(set (match_operand:DI 0 "register_operand" "=y,x,Yv") 21116 (unspec:DI [(match_operand:DI 1 "register_operand" "0,0,Yv") 21117 (match_operand:DI 2 "register_mmxmem_operand" "ym,x,Yv") 21118 (match_operand:SI 3 "const_0_to_255_mul_8_operand")] 21119 UNSPEC_PALIGNR))] 21120 "(TARGET_MMX || TARGET_MMX_WITH_SSE) && TARGET_SSSE3" Alternative 2 requires Yw instead of Yv since it's splitted to vpsrldq which requires AVX512VL & AVX512BW for evex version. gcc/ChangeLog: PR target/105854 * config/i386/sse.md (ssse3_palignrdi): Change alternative 2 from Yv to Yw.
next prev parent reply other threads:[~2022-06-08 3:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-05 9:28 [Bug target/105854] New: " zsojka at seznam dot cz 2022-06-06 3:47 ` [Bug target/105854] " crazylht at gmail dot com 2022-06-07 9:32 ` cvs-commit at gcc dot gnu.org 2022-06-08 2:59 ` cvs-commit at gcc dot gnu.org 2022-06-08 3:17 ` cvs-commit at gcc dot gnu.org 2022-06-08 3:17 ` cvs-commit at gcc dot gnu.org [this message] 2022-06-08 3:18 ` crazylht at gmail dot com 2022-07-05 17:02 ` cvs-commit at gcc dot gnu.org 2022-07-06 13:52 ` roger at nextmovesoftware dot com
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-105854-4-j22pB9aQCB@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).