From: Jeff Law <jeffreyalaw@gmail.com>
To: Jin Ma <jinma@linux.alibaba.com>, jinma <ijinma@yeah.net>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Vineet Gupta <vineetg@rivosinc.com>
Cc: "christoph.muellner" <christoph.muellner@vrull.eu>,
"kito.cheng" <kito.cheng@sifive.com>,
"kito.cheng" <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>
Subject: Re: [PATCH v9] RISC-V: Add the 'zfa' extension, version 0.2
Date: Mon, 14 Aug 2023 16:11:35 -0600 [thread overview]
Message-ID: <cba598a6-01a4-bd16-ac4e-0f5f749d3a7a@gmail.com> (raw)
In-Reply-To: <b17435ec-e557-4c8e-9d44-5c9d02eb56b4.jinma@linux.alibaba.com>
On 8/14/23 00:10, Jin Ma wrote:
> Additional links：
> v10, the patch that needs to be reviewed again:
> http://patchwork.ozlabs.org/project/gcc/patch/20230814055033.1995-1-jinma@linux.alibaba.com/
>
> v9 and the previous review comments:
> http://patchwork.ozlabs.org/project/gcc/patch/20230515131628.953-1-jinma@linux.alibaba.com/
>
> Zfa patch in master branch of binutils-gdb
> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=1f3fc45bddc7147a2e59346a59290094137ef1e1
Will do. We'll also have to evaluate against Tsukasa's work. As we saw
with Zicond there may be cases that are better handled by one vs the
other and we may end up taking pieces from both.
jeff
prev parent reply other threads:[~2023-08-14 22:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 9:57 [PATCH v8] " Jin Ma
2023-05-05 15:03 ` Christoph Müllner
2023-05-05 15:04 ` Christoph Müllner
2023-05-05 15:12 ` Palmer Dabbelt
2023-05-05 15:43 ` Christoph Müllner
2023-05-05 23:31 ` Jeff Law
2023-05-06 7:54 ` Jin Ma
2023-05-06 12:53 ` jinma
2023-05-16 3:59 ` Jeff Law
2023-05-15 13:16 ` [PATCH v9] " Jin Ma
2023-05-15 13:30 ` jinma
2023-05-16 4:00 ` Jeff Law
2023-05-16 4:16 ` Jeff Law
2023-05-16 7:06 ` jinma
2023-05-16 7:53 ` Kito Cheng
2023-08-09 18:11 ` Vineet Gupta
2023-08-11 15:49 ` Jin Ma
2023-08-14 6:00 ` Jin Ma
2023-08-14 6:10 ` Jin Ma
2023-08-14 22: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=cba598a6-01a4-bd16-ac4e-0f5f749d3a7a@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=ijinma@yeah.net \
--cc=jinma@linux.alibaba.com \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
--cc=vineetg@rivosinc.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).