public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: jiawei <jiawei@iscas.ac.cn>
Cc: gcc-patches@gcc.gnu.org, kito.cheng@sifive.com,
	palmer@rivosinc.com,  juzhe.zhong@rivai.ai,
	christoph.muellner@vrull.eu, wuwei2016@iscas.ac.cn
Subject: Re: [PATCH] RISC-V: Optimal RVV epilogue logic.
Date: Tue, 15 Nov 2022 11:35:49 +0100	[thread overview]
Message-ID: <CAAeLtUBGerbgr_0YEwtzHHTeCLC1iE+y-fLqiTx9hmojb31O5g@mail.gmail.com> (raw)
In-Reply-To: <20221114162918.1563116-1-jiawei@iscas.ac.cn>

On Mon, 14 Nov 2022 at 17:29, jiawei <jiawei@iscas.ac.cn> wrote:
>
> Skip add insn generate if the adjust size equal to zero.
>
> gcc/ChangeLog:
>
>         * config/riscv/riscv.cc (riscv_expand_epilogue):
>                                 New if control segement.
>
> ---
>  gcc/config/riscv/riscv.cc | 18 ++++++++++--------
>  1 file changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc
> index 02a01ca0b7c..af138db7545 100644
> --- a/gcc/config/riscv/riscv.cc
> +++ b/gcc/config/riscv/riscv.cc
> @@ -5186,24 +5186,26 @@ riscv_expand_epilogue (int style)
>         }
>
>        /* Get an rtx for STEP1 that we can add to BASE.  */
> -      rtx adjust = GEN_INT (step1.to_constant ());
> -      if (!SMALL_OPERAND (step1.to_constant ()))
> +      if (step1.to_constant () != 0){
> +        rtx adjust = GEN_INT (step1.to_constant ());
> +        if (!SMALL_OPERAND (step1.to_constant ()))

Please take a look at the recent improvements for the add<mode>3
expander (recently submitted as
https://patchwork.ozlabs.org/project/gcc/patch/20221109230718.3240479-1-philipp.tomsich@vrull.eu/).
Maybe you also want to use the test for the addi_operand(...) instead
of SMALL_OPERAND?

>         {
>           riscv_emit_move (RISCV_PROLOGUE_TEMP (Pmode), adjust);
>           adjust = RISCV_PROLOGUE_TEMP (Pmode);
>         }
>
> -      insn = emit_insn (
> +        insn = emit_insn (
>                gen_add3_insn (stack_pointer_rtx, stack_pointer_rtx, adjust));
>
> -      rtx dwarf = NULL_RTX;
> -      rtx cfa_adjust_rtx = gen_rtx_PLUS (Pmode, stack_pointer_rtx,
> +        rtx dwarf = NULL_RTX;
> +        rtx cfa_adjust_rtx = gen_rtx_PLUS (Pmode, stack_pointer_rtx,
>                                          GEN_INT (step2));
>
> -      dwarf = alloc_reg_note (REG_CFA_DEF_CFA, cfa_adjust_rtx, dwarf);
> -      RTX_FRAME_RELATED_P (insn) = 1;
> +        dwarf = alloc_reg_note (REG_CFA_DEF_CFA, cfa_adjust_rtx, dwarf);
> +        RTX_FRAME_RELATED_P (insn) = 1;
>
> -      REG_NOTES (insn) = dwarf;
> +        REG_NOTES (insn) = dwarf;
> +      }
>      }
>    else if (frame_pointer_needed)
>      {
> --
> 2.25.1
>

      parent reply	other threads:[~2022-11-15 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 16:29 jiawei
2022-11-15  1:48 ` Kito Cheng
2022-11-15  2:37   ` jiawei
2022-11-15  2:46     ` juzhe.zhong
2022-11-15  3:13       ` Kito Cheng
2022-11-15  3:42         ` Jeff Law
2022-11-15  3:30 ` Jeff Law
2022-11-15 10:35 ` Philipp Tomsich [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=CAAeLtUBGerbgr_0YEwtzHHTeCLC1iE+y-fLqiTx9hmojb31O5g@mail.gmail.com \
    --to=philipp.tomsich@vrull.eu \
    --cc=christoph.muellner@vrull.eu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jiawei@iscas.ac.cn \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@sifive.com \
    --cc=palmer@rivosinc.com \
    --cc=wuwei2016@iscas.ac.cn \
    /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).