From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: palmer <palmer@rivosinc.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
kito.cheng <kito.cheng@gmail.com>,
Kito.cheng <kito.cheng@sifive.com>,
jeffreyalaw <jeffreyalaw@gmail.com>,
"Robin Dapp" <rdapp.gcc@gmail.com>
Subject: Re: Re: [PATCH V2] RISC-V: Fix magic number of RVV auto-vectorization expander
Date: Wed, 24 May 2023 09:34:00 +0800 [thread overview]
Message-ID: <73D72E3260FA75C2+20230524093359966218180@rivai.ai> (raw)
In-Reply-To: <mhng-59246c46-142a-4d96-84f0-687264c2e666@palmer-ri-x1c9a>
[-- Attachment #1: Type: text/plain, Size: 7023 bytes --]
Yeah. Can I merge it?
juzhe.zhong@rivai.ai
From: Palmer Dabbelt
Date: 2023-05-24 09:32
To: juzhe.zhong
CC: gcc-patches; Kito Cheng; kito.cheng; jeffreyalaw; rdapp.gcc; juzhe.zhong
Subject: Re: [PATCH V2] RISC-V: Fix magic number of RVV auto-vectorization expander
On Tue, 23 May 2023 18:28:48 PDT (-0700), juzhe.zhong@rivai.ai wrote:
> From: Juzhe-Zhong <juzhe.zhong@rivai.ai>
>
> This simple patch fixes the magic number, remove magic number make codes more reasonable.
>
> Ok for trunk ?
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-v.cc (expand_vec_series): Remove magic number.
> (expand_const_vector): Ditto.
> (legitimize_move): Ditto.
> (sew64_scalar_helper): Ditto.
> (expand_tuple_move): Ditto.
> (expand_vector_init_insert_elems): Ditto.
> * config/riscv/riscv.cc (vector_zero_call_used_regs): Ditto.
>
> ---
> gcc/config/riscv/riscv-v.cc | 53 +++++++++++++++++--------------------
> gcc/config/riscv/riscv.cc | 2 +-
> 2 files changed, 26 insertions(+), 29 deletions(-)
>
> diff --git a/gcc/config/riscv/riscv-v.cc b/gcc/config/riscv/riscv-v.cc
> index 478a052a779..fa61a850a22 100644
> --- a/gcc/config/riscv/riscv-v.cc
> +++ b/gcc/config/riscv/riscv-v.cc
> @@ -406,14 +406,14 @@ expand_vec_series (rtx dest, rtx base, rtx step)
> int shift = exact_log2 (INTVAL (step));
> rtx shift_amount = gen_int_mode (shift, Pmode);
> insn_code icode = code_for_pred_scalar (ASHIFT, mode);
> - rtx ops[3] = {step_adj, vid, shift_amount};
> - emit_vlmax_insn (icode, riscv_vector::RVV_BINOP, ops);
> + rtx ops[] = {step_adj, vid, shift_amount};
> + emit_vlmax_insn (icode, RVV_BINOP, ops);
Looks like it also removes the "riscv_vector" namespace from some of the
constants? No big deal, it's just a different cleanup (assuming it
still builds and such).
> }
> else
> {
> insn_code icode = code_for_pred_scalar (MULT, mode);
> - rtx ops[3] = {step_adj, vid, step};
> - emit_vlmax_insn (icode, riscv_vector::RVV_BINOP, ops);
> + rtx ops[] = {step_adj, vid, step};
> + emit_vlmax_insn (icode, RVV_BINOP, ops);
> }
> }
>
> @@ -428,8 +428,8 @@ expand_vec_series (rtx dest, rtx base, rtx step)
> {
> rtx result = gen_reg_rtx (mode);
> insn_code icode = code_for_pred_scalar (PLUS, mode);
> - rtx ops[3] = {result, step_adj, base};
> - emit_vlmax_insn (icode, riscv_vector::RVV_BINOP, ops);
> + rtx ops[] = {result, step_adj, base};
> + emit_vlmax_insn (icode, RVV_BINOP, ops);
> emit_move_insn (dest, result);
> }
> }
> @@ -445,8 +445,8 @@ expand_const_vector (rtx target, rtx src)
> gcc_assert (
> const_vec_duplicate_p (src, &elt)
> && (rtx_equal_p (elt, const0_rtx) || rtx_equal_p (elt, const1_rtx)));
> - rtx ops[2] = {target, src};
> - emit_vlmax_insn (code_for_pred_mov (mode), riscv_vector::RVV_UNOP, ops);
> + rtx ops[] = {target, src};
> + emit_vlmax_insn (code_for_pred_mov (mode), RVV_UNOP, ops);
> return;
> }
>
> @@ -458,16 +458,14 @@ expand_const_vector (rtx target, rtx src)
> we use vmv.v.i instruction. */
> if (satisfies_constraint_vi (src) || satisfies_constraint_Wc0 (src))
> {
> - rtx ops[2] = {tmp, src};
> - emit_vlmax_insn (code_for_pred_mov (mode), riscv_vector::RVV_UNOP,
> - ops);
> + rtx ops[] = {tmp, src};
> + emit_vlmax_insn (code_for_pred_mov (mode), RVV_UNOP, ops);
> }
> else
> {
> elt = force_reg (elt_mode, elt);
> - rtx ops[2] = {tmp, elt};
> - emit_vlmax_insn (code_for_pred_broadcast (mode),
> - riscv_vector::RVV_UNOP, ops);
> + rtx ops[] = {tmp, elt};
> + emit_vlmax_insn (code_for_pred_broadcast (mode), RVV_UNOP, ops);
> }
>
> if (tmp != target)
> @@ -536,9 +534,8 @@ legitimize_move (rtx dest, rtx src)
> rtx tmp = gen_reg_rtx (mode);
> if (MEM_P (src))
> {
> - rtx ops[2] = {tmp, src};
> - emit_vlmax_insn (code_for_pred_mov (mode), riscv_vector::RVV_UNOP,
> - ops);
> + rtx ops[] = {tmp, src};
> + emit_vlmax_insn (code_for_pred_mov (mode), RVV_UNOP, ops);
> }
> else
> emit_move_insn (tmp, src);
> @@ -548,8 +545,8 @@ legitimize_move (rtx dest, rtx src)
> if (satisfies_constraint_vu (src))
> return false;
>
> - rtx ops[2] = {dest, src};
> - emit_vlmax_insn (code_for_pred_mov (mode), riscv_vector::RVV_UNOP, ops);
> + rtx ops[] = {dest, src};
> + emit_vlmax_insn (code_for_pred_mov (mode), RVV_UNOP, ops);
> return true;
> }
>
> @@ -813,7 +810,7 @@ sew64_scalar_helper (rtx *operands, rtx *scalar_op, rtx vl,
> *scalar_op = force_reg (scalar_mode, *scalar_op);
>
> rtx tmp = gen_reg_rtx (vector_mode);
> - rtx ops[3] = {tmp, *scalar_op, vl};
> + rtx ops[] = {tmp, *scalar_op, vl};
> riscv_vector::emit_nonvlmax_insn (code_for_pred_broadcast (vector_mode),
> riscv_vector::RVV_UNOP, ops);
> emit_vector_func (operands, tmp);
> @@ -1122,9 +1119,9 @@ expand_tuple_move (rtx *ops)
>
> if (fractional_p)
> {
> - rtx operands[3] = {subreg, mem, ops[4]};
> - emit_vlmax_insn (code_for_pred_mov (subpart_mode),
> - riscv_vector::RVV_UNOP, operands);
> + rtx operands[] = {subreg, mem, ops[4]};
> + emit_vlmax_insn (code_for_pred_mov (subpart_mode), RVV_UNOP,
> + operands);
> }
> else
> emit_move_insn (subreg, mem);
> @@ -1147,9 +1144,9 @@ expand_tuple_move (rtx *ops)
>
> if (fractional_p)
> {
> - rtx operands[3] = {mem, subreg, ops[4]};
> - emit_vlmax_insn (code_for_pred_mov (subpart_mode),
> - riscv_vector::RVV_UNOP, operands);
> + rtx operands[] = {mem, subreg, ops[4]};
> + emit_vlmax_insn (code_for_pred_mov (subpart_mode), RVV_UNOP,
> + operands);
> }
> else
> emit_move_insn (mem, subreg);
> @@ -1281,8 +1278,8 @@ expand_vector_init_insert_elems (rtx target, const rvv_builder &builder,
> unsigned int unspec
> = FLOAT_MODE_P (mode) ? UNSPEC_VFSLIDE1DOWN : UNSPEC_VSLIDE1DOWN;
> insn_code icode = code_for_pred_slide (unspec, mode);
> - rtx ops[3] = {target, target, builder.elt (i)};
> - emit_vlmax_insn (icode, riscv_vector::RVV_BINOP, ops);
> + rtx ops[] = {target, target, builder.elt (i)};
> + emit_vlmax_insn (icode, RVV_BINOP, ops);
> }
> }
>
> diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc
> index e7300b2e97c..09fc9e5d95e 100644
> --- a/gcc/config/riscv/riscv.cc
> +++ b/gcc/config/riscv/riscv.cc
> @@ -7396,7 +7396,7 @@ vector_zero_call_used_regs (HARD_REG_SET need_zeroed_hardregs)
> emitted_vlmax_vsetvl = true;
> }
>
> - rtx ops[3] = {target, CONST0_RTX (mode), vl};
> + rtx ops[] = {target, CONST0_RTX (mode), vl};
> riscv_vector::emit_vlmax_insn (code_for_pred_mov (mode),
> riscv_vector::RVV_UNOP, ops);
Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
as both cleanups look better to me. Thanks!
next prev parent reply other threads:[~2023-05-24 1:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 1:28 juzhe.zhong
2023-05-24 1:32 ` Palmer Dabbelt
2023-05-24 1:34 ` juzhe.zhong [this message]
2023-05-24 1:37 ` Palmer Dabbelt
2023-05-24 1:37 ` juzhe.zhong
2023-05-24 1:38 ` Palmer Dabbelt
[not found] ` <20230524093738744453181@rivai.ai>
2023-05-24 1:38 ` juzhe.zhong
2023-05-24 2:28 ` Li, Pan2
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=73D72E3260FA75C2+20230524093359966218180@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--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).