From: Jeff Law <jeffreyalaw@gmail.com>
To: Lehua Ding <lehua.ding@rivai.ai>, gcc-patches@gcc.gnu.org
Cc: juzhe.zhong@rivai.ai, rdapp.gcc@gmail.com, kito.cheng@gmail.com,
palmer@rivosinc.com
Subject: Re: [PATCH V2] RISC-V: Fix error combine of pred_mov pattern
Date: Mon, 28 Aug 2023 15:40:17 -0600 [thread overview]
Message-ID: <41332eb9-5971-b9e9-e2bc-f8175f0171fc@gmail.com> (raw)
In-Reply-To: <20230810122119.1679030-1-lehua.ding@rivai.ai>
On 8/10/23 06:21, Lehua Ding wrote:
> +;; vle.v/vse.v,vmv.v.v
> +(define_insn_and_split "*pred_mov<mode>"
> + [(set (match_operand:V_VLS 0 "nonimmediate_operand" "=vr, vr, vd, m, vr, vr")
> + (if_then_else:V_VLS
> + (unspec:<VM>
> + [(match_operand:<VM> 1 "vector_mask_operand" "vmWc1, Wc1, vm, vmWc1, Wc1, Wc1")
> + (match_operand 4 "vector_length_operand" " rK, rK, rK, rK, rK, rK")
> + (match_operand 5 "const_int_operand" " i, i, i, i, i, i")
> + (match_operand 6 "const_int_operand" " i, i, i, i, i, i")
> + (match_operand 7 "const_int_operand" " i, i, i, i, i, i")
> + (reg:SI VL_REGNUM)
> + (reg:SI VTYPE_REGNUM)] UNSPEC_VPREDICATE)
> + (match_operand:V_VLS 3 "reg_or_mem_operand" " m, m, m, vr, vr, vr")
> + (match_operand:V_VLS 2 "vector_merge_operand" " 0, vu, vu, vu, vu, 0")))]
> + "TARGET_VECTOR && (register_operand (operands[0], <MODE>mode)
> + || register_operand (operands[3], <MODE>mode))"
Just a formatting nit in the pattern's condition.
"(TARGET_VECTOR
&& (register_operand (operands[0], <MODE>mode)
|| register_operand (operands[3], <MODE>mode)))"
OK with that change. No need to wait for another approval. Just update
the patch, commit and post the committed patch to the list for archival
purposes.
Thanks, and sorry for the long wait. I just get busy sometimes.
jeff
prev parent reply other threads:[~2023-08-28 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 12:21 Lehua Ding
2023-08-28 2:21 ` Lehua Ding
2023-08-28 21:40 ` Jeff Law [this message]
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=41332eb9-5971-b9e9-e2bc-f8175f0171fc@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=lehua.ding@rivai.ai \
--cc=palmer@rivosinc.com \
--cc=rdapp.gcc@gmail.com \
/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).