From: Kito Cheng <kito.cheng@gmail.com>
To: Fei Gao <gaofei@eswincomputing.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, jiawei <jiawei@iscas.ac.cn>
Subject: Re: Re: [PATCH 0/2] support cm.push cm.pop cm.popret in zcmp and resolve confilct with shrink-wrap-separate
Date: Tue, 29 Aug 2023 10:41:12 +0800 [thread overview]
Message-ID: <CA+yXCZC-HsQC1GuYj40+ruD1ArgM0TyWd-D388DsG59s6z0M9A@mail.gmail.com> (raw)
In-Reply-To: <2023082818365042600523@eswincomputing.com>
> 1. flag_shrink_wrap_separate seems better than flag_shrink_wrap.
(flag_)shrink_wrap_separate seems a sub optimization of
(flag_)shrink_wrap, so I am fine if flag_shrink_wrap_separate is
enough.
> 2. to pass the zcmp testcases, i will add fno-shrink-wrap-separate option.
OK
prev parent reply other threads:[~2023-08-29 2:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 7:47 Fei Gao
2023-08-28 7:47 ` [PATCH 1/2] allow targets to check shrink-wrap-separate enabled or not Fei Gao
2023-08-28 22:54 ` Jeff Law
2023-08-29 1:28 ` Fei Gao
2023-08-29 1:46 ` Jeff Law
2023-09-01 1:20 ` Fei Gao
2023-08-28 7:47 ` [PATCH 2/2][V5][RISC-V]support cm.push cm.pop cm.popret in zcmp and resolve confilct with shrink-wrap-separate Fei Gao
2023-08-28 9:27 ` [PATCH 0/2] support " Kito Cheng
2023-08-28 10:36 ` Fei Gao
2023-08-29 2:41 ` 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+yXCZC-HsQC1GuYj40+ruD1ArgM0TyWd-D388DsG59s6z0M9A@mail.gmail.com \
--to=kito.cheng@gmail.com \
--cc=gaofei@eswincomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@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).