public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <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: Wed, 26 Oct 2022 08:46:50 +0000 [thread overview] Message-ID: <bug-107057-4-ggORtl4FE5@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 #7 from Hongtao.liu <crazylht at gmail dot com> --- And it looks like the pattern is wrongly defined since from [1]. ----------cut begin------------ 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. ----------------cut end---------- (define_insn "vec_concatv2df" [(set (match_operand:V2DF 0 "register_operand" "=x,x,v,x,v,x,x, v,x,x") (vec_concat:V2DF (match_operand:DF 1 "nonimmediate_operand" " 0,x,v,m,m,0,x,vm,0,0") (match_operand:DF 2 "nonimm_or_0_operand" " x,x,v,1,1,m,m, C,x,m")))] For alternatvie 1, the two operands are both input only. [1] https://gcc.gnu.org/onlinedocs/gccint/Simple-Constraints.html#Simple-Constraints
next prev parent reply other threads:[~2022-10-26 8:46 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 [this message] 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 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-ggORtl4FE5@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).