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 rtl-optimization/107057] [10/11/12/13 Regression] ICE in extract_constrain_insn, at recog.cc:2692 Date: Tue, 01 Nov 2022 05:34:52 +0000 [thread overview] Message-ID: <bug-107057-4-OwLouYMhkq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107057-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107057 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:4acc4c2be84d66075d60736623c3a7134d129eaa commit r13-3587-g4acc4c2be84d66075d60736623c3a7134d129eaa Author: liuhongt <hongtao.liu@intel.com> Date: Tue Oct 25 17:10:23 2022 +0800 Fix incorrect digit constraint Matching constraints are used in these circumstances. More precisely, the two operands that match must include one input-only operand and one output-only operand. Moreover, the digit must be a smaller number than the number of the operand that uses it in the constraint. In pr107057, the 2 operands in the pattern are both input operands. gcc/ChangeLog: PR target/107057 * config/i386/sse.md (*vec_interleave_highv2df): Remove constraint 1. (*vec_interleave_lowv2df): Ditto. (vec_concatv2df): Ditto. (*avx512f_unpcklpd512<mask_name>): Ditto and renamed to .. (avx512f_unpcklpd512<mask_name>): .. this. (avx512f_movddup512<mask_name>): Change to define_insn. (avx_movddup256<mask_name>): Ditto. (*avx_unpcklpd256<mask_name>): Remove constraint 1 and renamed to .. (avx_unpcklpd256<mask_name>): .. this. * config/i386/i386.cc (ix86_vec_interleave_v2df_operator_ok): Disallow MEM_P (op1) && MEM_P (op2). gcc/testsuite/ChangeLog: * gcc.target/i386/pr107057.c: New test.
next prev parent reply other threads:[~2022-11-01 5:34 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-27 16:25 [Bug c/107057] New: " gscfq@t-online.de 2022-09-27 16:30 ` [Bug target/107057] " pinskia at gcc dot gnu.org 2022-09-29 8:00 ` rguenth at gcc dot gnu.org 2022-09-29 11:41 ` marxin at gcc dot gnu.org 2022-09-29 12:52 ` ubizjak at gmail dot com 2022-09-29 15:01 ` [Bug rtl-optimization/107057] " ubizjak at gmail dot com 2022-10-19 6:28 ` crazylht at gmail dot com 2022-10-25 9:15 ` crazylht at gmail dot com 2022-10-26 2:16 ` crazylht at gmail dot com 2022-10-26 8:46 ` crazylht at gmail dot com 2022-10-26 8:47 ` crazylht at gmail dot com 2022-10-28 8:38 ` ubizjak at gmail dot com 2022-11-01 5:34 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-01 5:38 ` crazylht at gmail dot com 2023-07-07 10:44 ` [Bug rtl-optimization/107057] [11/12 " rguenth at gcc dot gnu.org 2023-11-30 10:43 ` liuhongt 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-107057-4-OwLouYMhkq@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).