From: Fei Gao <gaofei@eswincomputing.com>
To: gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, palmer@dabbelt.com, jeffreyalaw@gmail.com,
sinan.lin@linux.alibaba.com, jiawei@iscas.ac.cn,
Fei Gao <gaofei@eswincomputing.com>
Subject: [PATCH 0/2] resolve confilct between zcmp multi push/pop and shrink-wrap-separate
Date: Wed, 6 Sep 2023 09:39:07 +0000 [thread overview]
Message-ID: <20230906093909.32207-1-gaofei@eswincomputing.com> (raw)
Enable muti push and pop for Zcmp when shrink-wrap-separate is ineffective.
Fei Gao (2):
allow targets to check shrink-wrap-separate enabled or not
[V2][RISC-V] enable muti push and pop for Zcmp when shrink-wrap-separate is ineffective
gcc/config/riscv/riscv.cc | 21 ++++-
gcc/shrink-wrap.cc | 22 +++--
gcc/shrink-wrap.h | 1 +
gcc/testsuite/gcc.target/riscv/rv32e_zcmp.c | 2 +-
gcc/testsuite/gcc.target/riscv/rv32i_zcmp.c | 2 +-
.../gcc.target/riscv/zcmp_push_fpr.c | 2 +-
.../riscv/zcmp_shrink_wrap_separate.c | 93 +++++++++++++++++++
.../riscv/zcmp_shrink_wrap_separate2.c | 93 +++++++++++++++++++
.../gcc.target/riscv/zcmp_stack_alignment.c | 2 +-
9 files changed, 223 insertions(+), 15 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/riscv/zcmp_shrink_wrap_separate.c
create mode 100644 gcc/testsuite/gcc.target/riscv/zcmp_shrink_wrap_separate2.c
--
2.17.1
next reply other threads:[~2023-09-06 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 9:39 Fei Gao [this message]
2023-09-06 9:39 ` [PATCH 1/2] allow targets to check shrink-wrap-separate enabled or not Fei Gao
2023-09-06 9:39 ` [PATCH 2/2] [V2][RISC-V] enable muti push and pop for Zcmp when shrink-wrap-separate is ineffective Fei Gao
2023-09-12 1:58 ` [PATCH 0/2] resolve confilct between zcmp multi push/pop and shrink-wrap-separate Kito Cheng
-- strict thread matches above, loose matches on Subject: below --
2023-08-31 6:24 Fei Gao
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=20230906093909.32207-1-gaofei@eswincomputing.com \
--to=gaofei@eswincomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=sinan.lin@linux.alibaba.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).