From: Kito Cheng <kito.cheng@gmail.com>
To: "Christoph Müllner" <christoph.muellner@vrull.eu>
Cc: Kito Cheng <kito.cheng@sifive.com>,
gcc-patches@gcc.gnu.org, palmer@dabbelt.com,
jeffreyalaw@gmail.com
Subject: Re: [PATCH] RISC-V: Save/restore ra register correctly [PR112478]
Date: Thu, 16 Nov 2023 19:39:36 +0800 [thread overview]
Message-ID: <CA+yXCZCZTpv+WFWb++kAxhHMP540rHGdEza9GCjRVyy0cYJOew@mail.gmail.com> (raw)
In-Reply-To: <CAEg0e7iY1VtxVCc3DJemtyuQ2jztP+mrMRtA2s04sGUPKY=-WQ@mail.gmail.com>
Committed, thanks for the review and test :)
On Thu, Nov 16, 2023 at 7:19 AM Christoph Müllner
<christoph.muellner@vrull.eu> wrote:
>
> On Tue, Nov 14, 2023 at 3:15 PM Kito Cheng <kito.cheng@sifive.com> wrote:
> >
> > We set ra to fixed register now, but we still need to save/restore that at
> > prologue/epilogue if that has used.
>
> So before 71f906498ada9 $ra was neither a fixed nor a used register.
> Therefore, riscv_save_reg_p returned true in the first test (not global reg,
> not used_or_fixed, and ever_live_p).
> After this commit, this does not happen anymore, because the test for
> not used_or_fixed fails and we don't test for ever_live_p in the following.
> And this patch restores this behavior.
>
> Reviewed-by: Christoph Müllner <christoph.muellner@vrull.eu>
> Tested-by: Christoph Müllner <christoph.muellner@vrull.eu>
>
> >
> > gcc/ChangeLog:
> >
> > PR target/112478
> > * config/riscv/riscv.cc (riscv_save_return_addr_reg_p): Check ra
> > is ever lived.
> >
> > gcc/testsuite/gcc/ChangeLog:
> >
> > PR target/112478
> > * riscv/pr112478.c: New.
> > ---
> > gcc/config/riscv/riscv.cc | 4 ++++
> > gcc/testsuite/gcc.target/riscv/pr112478.c | 8 ++++++++
> > 2 files changed, 12 insertions(+)
> > create mode 100644 gcc/testsuite/gcc.target/riscv/pr112478.c
> >
> > diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc
> > index ecee7eb4727..f09c4066903 100644
> > --- a/gcc/config/riscv/riscv.cc
> > +++ b/gcc/config/riscv/riscv.cc
> > @@ -5802,6 +5802,10 @@ riscv_save_return_addr_reg_p (void)
> > if (riscv_far_jump_used_p ())
> > return true;
> >
> > + /* We need to save it if anyone has used that. */
> > + if (df_regs_ever_live_p (RETURN_ADDR_REGNUM))
> > + return true;
> > +
> > /* Need not to use ra for leaf when frame pointer is turned off by
> > option whatever the omit-leaf-frame's value. */
> > if (frame_pointer_needed && crtl->is_leaf
> > diff --git a/gcc/testsuite/gcc.target/riscv/pr112478.c b/gcc/testsuite/gcc.target/riscv/pr112478.c
> > new file mode 100644
> > index 00000000000..0bbde20b71b
> > --- /dev/null
> > +++ b/gcc/testsuite/gcc.target/riscv/pr112478.c
> > @@ -0,0 +1,8 @@
> > +/* { dg-do compile } */
> > +/* { dg-options "-ffat-lto-objects" } */
> > +
> > +void foo() {
> > + asm volatile("# " : ::"ra");
> > +}
> > +
> > +/* { dg-final { scan-assembler "s(w|d)\[ \t\]*ra" } } */
> > --
> > 2.40.1
> >
prev parent reply other threads:[~2023-11-16 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 14:14 Kito Cheng
2023-11-15 23:19 ` Christoph Müllner
2023-11-16 11:39 ` 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+yXCZCZTpv+WFWb++kAxhHMP540rHGdEza9GCjRVyy0cYJOew@mail.gmail.com \
--to=kito.cheng@gmail.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@sifive.com \
--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).