From: Jeff Law <jeffreyalaw@gmail.com>
To: Fei Gao <gaofei@eswincomputing.com>, gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, palmer@dabbelt.com
Subject: Re: [PATCH] [RISC-V] correct machine mode in save-restore cfi RTL.
Date: Mon, 5 Jun 2023 20:11:44 -0600 [thread overview]
Message-ID: <86b69681-5dd3-eb6d-299a-edf748a4506e@gmail.com> (raw)
In-Reply-To: <20230606015723.12297-1-gaofei@eswincomputing.com>
On 6/5/23 19:57, Fei Gao wrote:
> gcc/ChangeLog:
>
> * config/riscv/riscv.cc (riscv_adjust_libcall_cfi_prologue): use Pmode for cfi reg/mem machmode
> (riscv_adjust_libcall_cfi_epilogue): use Pmode for cfi reg machmode
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/save-restore-cfi-2.c: New test to check machmode for cfi reg/mem.
I rewrapped the ChangeLog to 80 columns and reindented the arguments to
the gen_frame_mem call to match our formatting guidelines.
Pushed to the trunk.
Thanks,
jeff
prev parent reply other threads:[~2023-06-06 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 1:57 Fei Gao
2023-06-06 2:11 ` Jeff Law [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=86b69681-5dd3-eb6d-299a-edf748a4506e@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gaofei@eswincomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.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).