From: Jeff Law <jeffreyalaw@gmail.com>
To: Fei Gao <gaofei@eswincomputing.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Kito Cheng <kito.cheng@gmail.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Sinan <sinan.lin@linux.alibaba.com>, jiawei <jiawei@iscas.ac.cn>
Subject: Re: [PATCH 1/2] allow target to check shrink-wrap-separate enabled or not
Date: Mon, 28 Aug 2023 16:32:29 -0600 [thread overview]
Message-ID: <53cee14f-4e92-473a-3927-0555d916d5ea@gmail.com> (raw)
In-Reply-To: <2023062610290920752436@eswincomputing.com>
On 6/25/23 20:29, Fei Gao wrote:
> hi Jeff
>
> Please see my earlier reply here.
> https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg310656.html
>
> Maybe you scrolled past it in so many emails:)
Oh, so the issue isn't really the set of components being wrapped, but
the way in which we save them. Yea, that's going to need some tinkering.
It does make me wonder if we can handle this in riscv_override_options.
That's a pretty standard place to deal with option conflicts. We ought
to be able to check if both options are enabled, then disable zcmp
push/pop at that poing without introducing any new hooks.
jeff
next prev parent reply other threads:[~2023-08-28 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 9:40 [PATCH 0/2] resolve confilct between RISC-V zcmp and shrink-wrap-separate Fei Gao
2023-06-20 9:40 ` [PATCH 1/2] allow target to check shrink-wrap-separate enabled or not Fei Gao
2023-06-25 13:36 ` Jeff Law
2023-06-26 2:29 ` Fei Gao
2023-08-28 22:03 ` Jeff Law
2023-08-28 22:32 ` Jeff Law [this message]
2023-06-20 9:40 ` [PATCH 2/2] [RISC-V] resolve confilct between zcmp multi push/pop and shrink-wrap-separate 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=53cee14f-4e92-473a-3927-0555d916d5ea@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gaofei@eswincomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--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).