public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107057] [10/11/12/13 Regression] ICE in extract_constrain_insn, at recog.cc:2692
Date: Thu, 29 Sep 2022 12:52:41 +0000 [thread overview]
Message-ID: <bug-107057-4-ZNFnllD7Zj@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 #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
Reload starts with:
(insn 76 67 101 5 (set (reg/v:V2DF 108 [ x ])
(vec_concat:V2DF (reg:DF 182)
(reg:DF 182))) "pr107057.c":7:10 5952 {vec_concatv2df}
(expr_list:REG_EQUAL (const_vector:V2DF [
(const_double:DF 1.0e+0 [0x0.8p+1]) repeated x2
])
(nil)))
And reloads the insn with:
(insn 392 67 393 5 (set (reg:DI 0 ax [330])
(symbol_ref/u:DI ("*.LC0") [flags 0x2])) "pr107057.c":7:10 82
{*movdi_internal}
(nil))
(insn 407 393 76 5 (set (reg:DI 4 si [331])
(reg:DI 0 ax [330])) "pr107057.c":7:10 82 {*movdi_internal}
(nil))
(insn 76 407 101 5 (set (reg/v:V2DF 24 xmm4 [orig:108 x ] [108])
(vec_concat:V2DF (mem/u/c:DF (reg:DI 0 ax [330]) [0 S8 A64])
(mem/u/c:DF (reg:DI 4 si [331]) [0 S8 A64]))) "pr107057.c":7:10
5952 {vec_concatv2df}
(expr_list:REG_EQUAL (const_vector:V2DF [
(const_double:DF 1.0e+0 [0x0.8p+1]) repeated x2
])
(nil)))
Non-matching mem RTXes violate the candidate (x,m,1) constraint (and also insn
constraint):
(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")))]
"TARGET_SSE
&& (!(MEM_P (operands[1]) && MEM_P (operands[2]))
|| (TARGET_SSE3 && rtx_equal_p (operands[1], operands[2])))"
next prev parent reply other threads:[~2022-09-29 12:52 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 [this message]
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
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-ZNFnllD7Zj@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: link
Be 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).