From: Kito Cheng <kito.cheng@gmail.com>
To: juzhe.zhong@rivai.ai
Cc: gcc-patches@gcc.gnu.org, palmer@dabbelt.com
Subject: Re: [PATCH] RISC-V: Refine function args of some functions.
Date: Fri, 27 Jan 2023 18:05:56 +0800 [thread overview]
Message-ID: <CA+yXCZDvdB4cckF30dV-i-_EU2yEhpHmJvLh=rW7ys7sxUW6DA@mail.gmail.com> (raw)
In-Reply-To: <20230118031305.69740-1-juzhe.zhong@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]
committed, thanks!
On Wed, Jan 18, 2023 at 11:13 AM <juzhe.zhong@rivai.ai> wrote:
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc (gen_vsetvl_pat): Refine function
> args.
> (emit_vsetvl_insn): Ditto.
>
> ---
> gcc/config/riscv/riscv-vsetvl.cc | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/gcc/config/riscv/riscv-vsetvl.cc
> b/gcc/config/riscv/riscv-vsetvl.cc
> index 728a32dacd6..e11751f00af 100644
> --- a/gcc/config/riscv/riscv-vsetvl.cc
> +++ b/gcc/config/riscv/riscv-vsetvl.cc
> @@ -580,7 +580,7 @@ has_vector_insn (function *fn)
>
> /* Emit vsetvl instruction. */
> static rtx
> -gen_vsetvl_pat (enum vsetvl_type insn_type, vl_vtype_info info, rtx vl)
> +gen_vsetvl_pat (enum vsetvl_type insn_type, const vl_vtype_info &info,
> rtx vl)
> {
> rtx avl = info.get_avl ();
> rtx sew = gen_int_mode (info.get_sew (), Pmode);
> @@ -600,7 +600,7 @@ gen_vsetvl_pat (enum vsetvl_type insn_type,
> vl_vtype_info info, rtx vl)
> }
>
> static rtx
> -gen_vsetvl_pat (rtx_insn *rinsn, const vector_insn_info info)
> +gen_vsetvl_pat (rtx_insn *rinsn, const vector_insn_info &info)
> {
> rtx new_pat;
> if (vsetvl_insn_p (rinsn) || vlmax_avl_p (info.get_avl ()))
> @@ -617,7 +617,7 @@ gen_vsetvl_pat (rtx_insn *rinsn, const
> vector_insn_info info)
>
> static void
> emit_vsetvl_insn (enum vsetvl_type insn_type, enum emit_type emit_type,
> - vl_vtype_info info, rtx vl, rtx_insn *rinsn)
> + const vl_vtype_info &info, rtx vl, rtx_insn *rinsn)
> {
> rtx pat = gen_vsetvl_pat (insn_type, info, vl);
> if (dump_file)
> --
> 2.36.3
>
>
>
prev parent reply other threads:[~2023-01-27 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 3:13 juzhe.zhong
2023-01-27 10:05 ` Kito Cheng [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='CA+yXCZDvdB4cckF30dV-i-_EU2yEhpHmJvLh=rW7ys7sxUW6DA@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=palmer@dabbelt.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).