public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pan2.li at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114714] [RISC-V][RVV] ICE: insn does not satisfy its constraints (postreload) Date: Mon, 15 Apr 2024 10:30:57 +0000 [thread overview] Message-ID: <bug-114714-4-Og81EL1WYE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114714-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114714 --- Comment #2 from Li Pan <pan2.li at intel dot com> --- The vzext.vf2 has earlyclobber dest operand, and then it cannot allocated to the source operand, like vzext.vf2 v0, v0. Thus we will fail when check_rtl. (define_insn "@pred_<optab><mode>_vf2" [(set (match_operand:VWEXTI 0 "register_operand" "=vd, vr, vd, vr, vd, vr, vd, vr, vd, vr, vd, vr, ?&vr, ?&vr") ........(if_then_else:VWEXTI ........ (unspec:<VM> ........ [(match_operand:<VM> 1 "vector_mask_operand" " vm,Wc1, vm,Wc1, vm,Wc1, vm,Wc1, vm,Wc1, vm,Wc1,vmWc1,vmWc1") ........ (match_operand 4 "vector_length_operand" " rK, rK, rK, rK, rK, rK, rK, rK, rK, rK, rK, rK, rK, rK") ........ (match_operand 5 "const_int_operand" "i, i, i, i, i, i, i, i, i, i, i, i, i, i") ........ (match_operand 6 "const_int_operand" "i, i, i, i, i, i, i, i, i, i, i, i, i, i") ........ (match_operand 7 "const_int_operand" "i, i, i, i, i, i, i, i, i, i, i, i, i, i") ........ (reg:SI VL_REGNUM) ........ (reg:SI VTYPE_REGNUM)] UNSPEC_VPREDICATE) ........ (any_extend:VWEXTI ........ (match_operand:<V_DOUBLE_TRUNC> 3 "register_operand" "W21,W21,W21,W21,W42,W42,W42,W42,W84,W84,W84,W84, vr, vr")) ........ (match_operand:VWEXTI 2 "vector_merge_operand" " vu, vu, 0, 0, vu, vu, 0, 0, vu, vu, 0, 0, vu, 0")))] "TARGET_VECTOR" "v<sz>ext.vf2\t%0,%3%p1" [(set_attr "type" "vext") (set_attr "mode" "<MODE>") (set_attr "group_overlap" "W21,W21,W21,W21,W42,W42,W42,W42,W84,W84,W84,W84,none,none")]) ---------------------------------------------------------------------------------------------------- insn 1205 1214 5405 70 (set (reg:RVVM1SI 97 v1 [orig:687 _1177 ] [687]) (if_then_else:RVVM1SI (unspec:RVVMF32BI [ (const_vector:RVVMF32BI repeat [ (const_int 1 [0x1]) ]) (reg:DI 25 s9 [orig:539 _889 ] [539]) (const_int 2 [0x2]) repeated x2 (const_int 0 [0]) (reg:SI 66 vl) (reg:SI 67 vtype) ] UNSPEC_VPREDICATE) (zero_extend:RVVM1SI (reg:RVVMF2HI 97 v1 [orig:654 _1100 ] [654])) (unspec:RVVM1SI [ (reg:DI 0 zero) ] UNSPEC_VUNDEF))) "../hwy/ops/rvv-inl.h":1964:386 discrim 1 8452 {pred_zero_extendrvvm1si_vf2} (nil)) during RTL pass: reload
next prev parent reply other threads:[~2024-04-15 10:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-14 16:49 [Bug target/114714] New: " schwab@linux-m68k.org 2024-04-15 1:34 ` [Bug target/114714] " pan2.li at intel dot com 2024-04-15 10:30 ` pan2.li at intel dot com [this message] 2024-04-15 13:47 ` kito at gcc dot gnu.org 2024-04-15 14:09 ` pan2.li at intel dot com 2024-04-22 12:56 ` rdapp at gcc dot gnu.org 2024-04-22 22:16 ` juzhe.zhong at rivai dot ai 2024-04-25 10:14 ` cvs-commit 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-114714-4-Og81EL1WYE@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).