From: Jeff Law <jeffreyalaw@gmail.com>
To: Philipp Tomsich <philipp.tomsich@vrull.eu>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
christoph.muellner@vrull.eu, binutils@sourceware.org,
nelson@rivosinc.com, Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
jbeulich@suse.com, Kito Cheng <kito.cheng@gmail.com>,
research_trasio@irq.a4lg.com
Subject: Re: [RFC PATCH v5] RISC-V: Add support for the Zfa extension
Date: Fri, 30 Jun 2023 08:39:18 -0600 [thread overview]
Message-ID: <d1661ae5-a1ea-f0df-6c5b-2fdba55a8f79@gmail.com> (raw)
In-Reply-To: <CAAeLtUChQ9wUD6BjoD82J9n-9DwiziHnCi_F2EuSF9U3uBP32Q@mail.gmail.com>
On 6/30/23 08:08, Philipp Tomsich wrote:
> I added a small change to list this in binutils/NEWS.
> Please check if we added other extensions in this release that are
> missing from there.
Yea, it's probably worth a top-to-bottom review for extensions.
We've got an interest in seeing vector crypto move forward and we've
been using your team's patches to-date. So I'll take a look at those next.
Zc* is also out there. They're lower priority for Ventana than vector
crypto and more importantly I think Nelson has some state on them. So
I'll leave them in his hands.
jeff
next prev parent reply other threads:[~2023-06-30 14:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 13:36 Christoph Muellner
2023-06-29 7:52 ` Christoph Müllner
2023-06-29 8:33 ` Christoph Müllner
2023-06-29 15:07 ` Jeff Law
2023-06-29 15:10 ` Christoph Müllner
2023-06-29 15:37 ` Palmer Dabbelt
2023-06-29 15:49 ` Jeff Law
2023-06-29 15:51 ` Philipp Tomsich
2023-06-30 13:40 ` Jeff Law
2023-06-30 14:06 ` Jeff Law
2023-06-30 14:08 ` Philipp Tomsich
2023-06-30 14:39 ` Jeff Law [this message]
2023-06-29 15:52 ` Palmer Dabbelt
2023-06-29 16:03 ` Jeff Law
2023-06-29 16:12 ` Palmer Dabbelt
2023-06-30 14:07 ` Philipp Tomsich
2023-06-30 0:47 ` Nelson Chu
2023-06-30 6:49 ` Kito Cheng
2023-06-30 13:38 ` 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=d1661ae5-a1ea-f0df-6c5b-2fdba55a8f79@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=christoph.muellner@vrull.eu \
--cc=jbeulich@suse.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=nelson@rivosinc.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=research_trasio@irq.a4lg.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).