From: Jeff Law <jeffreyalaw@gmail.com>
To: yanzhang.wang@intel.com, gcc-patches@gcc.gnu.org
Cc: juzhe.zhong@rivai.ai, kito.cheng@sifive.com, pan2.li@intel.com
Subject: Re: [PATCH v3] RISC-V: Fix regression of -fzero-call-used-regs=all
Date: Sat, 8 Apr 2023 12:39:49 -0600 [thread overview]
Message-ID: <f2051621-63a8-e447-e08a-2d449e5374d5@gmail.com> (raw)
In-Reply-To: <20230407123249.2600968-1-yanzhang.wang@intel.com>
On 4/7/23 06:32, yanzhang.wang--- via Gcc-patches wrote:
> From: Yanzhang Wang <yanzhang.wang@intel.com>
>
> This patch registers a riscv specific function to
> TARGET_ZERO_CALL_USED_REGS instead of default in targhooks.cc. It will
> clean gpr and vector relevant registers.
>
> PR 109104
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-protos.h (emit_hard_vlmax_vsetvl):
> * config/riscv/riscv-v.cc (emit_hard_vlmax_vsetvl):
> (emit_vlmax_vsetvl):
> * config/riscv/riscv.cc (vector_zero_call_used_regs):
> (riscv_zero_call_used_regs):
> (TARGET_ZERO_CALL_USED_REGS):
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/zero-scratch-regs-1.c: New test.
> * gcc.target/riscv/zero-scratch-regs-2.c: New test.
> * gcc.target/riscv/zero-scratch-regs-3.c: New test.
Presumably the difficulty here is we need to find a suitable hard
register so that we can emit the vsetvl.
>
> Signed-off-by: Yanzhang Wang <yanzhang.wang@intel.com>
> Co-authored-by: Pan Li <pan2.li@intel.com>
> Co-authored-by: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
> Co-authored-by: Kito Cheng <kito.cheng@sifive.com>
> ---
> gcc/config/riscv/riscv-protos.h | 1 +
> gcc/config/riscv/riscv-v.cc | 15 +++-
> gcc/config/riscv/riscv.cc | 71 +++++++++++++++++++
> .../gcc.target/riscv/zero-scratch-regs-1.c | 9 +++
> .../gcc.target/riscv/zero-scratch-regs-2.c | 24 +++++++
> .../gcc.target/riscv/zero-scratch-regs-3.c | 57 +++++++++++++++
> 6 files changed, 174 insertions(+), 3 deletions(-)
> create mode 100644 gcc/testsuite/gcc.target/riscv/zero-scratch-regs-1.c
> create mode 100644 gcc/testsuite/gcc.target/riscv/zero-scratch-regs-2.c
> create mode 100644 gcc/testsuite/gcc.target/riscv/zero-scratch-regs-3.c
>
> diff --git a/gcc/config/riscv/riscv-v.cc b/gcc/config/riscv/riscv-v.cc
> index 2e91d019f6c..13dd6639c9f 100644
> --- a/gcc/config/riscv/riscv-v.cc
> +++ b/gcc/config/riscv/riscv-v.cc
> @@ -118,6 +118,17 @@ const_vec_all_same_in_range_p (rtx x, HOST_WIDE_INT minval,
> && IN_RANGE (INTVAL (elt), minval, maxval));
> }
>
> +/* Emit a vlmax vsetvl instruction with side effect, this should be only used
> + when optimization is tune off or emit after vsetvl insertion pass. */
Minor grammar errors. I'd probably write it as:
/* Emit a vlvax vsetvl instruction. This should only be used
when optimization is disabled or after the vsetvl insertion pass. */
Do you need to save/restore the vector configuration before and after
clearing the vector registers? If so, that seems to be missing. If
not, it seems like a comment explaining why would be useful.
Jeff
next prev parent reply other threads:[~2023-04-08 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 13:34 [PATCH] " yanzhang.wang
2023-04-06 13:47 ` juzhe.zhong
2023-04-06 14:59 ` Kito Cheng
2023-04-07 6:59 ` [PATCH v2] " yanzhang.wang
2023-04-07 7:07 ` Kito Cheng
2023-04-07 12:32 ` [PATCH v3] " yanzhang.wang
2023-04-08 18:39 ` Jeff Law [this message]
2023-04-10 2:21 ` Wang, Yanzhang
2023-04-10 3:11 ` Kito Cheng
2023-04-10 20:57 ` Jeff Law
2023-04-10 3:00 ` [PATCH v4] " yanzhang.wang
2023-04-11 11:37 ` [PATCH v5] " yanzhang.wang
2023-04-11 12:00 ` Wang, Yanzhang
2023-04-11 14:11 ` Kito Cheng
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=f2051621-63a8-e447-e08a-2d449e5374d5@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@sifive.com \
--cc=pan2.li@intel.com \
--cc=yanzhang.wang@intel.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).