From: Fei Gao <gaofei@eswincomputing.com>
To: gcc-patches@gcc.gnu.org
Cc: jeffreyalaw@gmail.com, kito.cheng@gmail.com, palmer@dabbelt.com,
Fei Gao <gaofei@eswincomputing.com>
Subject: [PATCH 0/3] RISC-V: optimize stack manipulation in save-restore
Date: Thu, 1 Dec 2022 10:03:29 +0000 [thread overview]
Message-ID: <20221201100332.22226-1-gaofei@eswincomputing.com> (raw)
The patches allow less instructions to be used in stack allocation
and deallocation if save-restore enabled, and also make the stack
manipulation codes more readable.
Fei Gao (3):
RISC-V: add a new parameter in riscv_first_stack_step.
RISC-V: optimize stack manipulation in save-restore
RISC-V: make the stack manipulation codes more readable.
gcc/config/riscv/riscv.cc | 105 +++++++++---------
.../gcc.target/riscv/stack_save_restore.c | 40 +++++++
2 files changed, 95 insertions(+), 50 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/riscv/stack_save_restore.c
--
2.17.1
next reply other threads:[~2022-12-01 10:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 10:03 Fei Gao [this message]
2022-12-01 10:03 ` [PATCH 1/3] RISC-V: add a new parameter in riscv_first_stack_step Fei Gao
2023-02-03 8:52 ` [PING][PATCH " Fei Gao
2023-04-16 16:40 ` [PATCH " Jeff Law
2023-04-17 18:09 ` Jeff Law
2022-12-01 10:03 ` [PATCH 2/3] RISC-V: optimize stack manipulation in save-restore Fei Gao
2023-02-03 8:52 ` [PING] " Fei Gao
2023-04-16 16:45 ` Jeff Law
2023-04-17 22:51 ` Jeff Law
2022-12-01 10:03 ` [PATCH 3/3] RISC-V: make the stack manipulation codes more readable Fei Gao
2023-02-03 8:52 ` [PING] " Fei Gao
2023-04-18 0:14 ` Jeff Law
2023-02-03 8:52 ` [PING] [PATCH 0/3] RISC-V: optimize stack manipulation in save-restore Fei Gao
2023-02-09 2:21 ` [PING 2] " Fei Gao
2023-02-16 7:17 ` Fei Gao
2023-02-16 14:39 ` Jeff Law
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=20221201100332.22226-1-gaofei@eswincomputing.com \
--to=gaofei@eswincomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--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).