From: Palmer Dabbelt <palmer@dabbelt.com>
To: jeffreyalaw@gmail.com
Cc: philipp.tomsich@vrull.eu, binutils@sourceware.org,
christoph.muellner@vrull.eu, kito.cheng@sifive.com,
nelson@rivosinc.com
Subject: Re: [RFC PATCH v1] RISC-V: Support Zicond extension
Date: Tue, 27 Jun 2023 16:33:40 -0700 (PDT) [thread overview]
Message-ID: <mhng-eb02047f-8515-4668-850a-a4e792e5fd40@palmer-ri-x1c9> (raw)
In-Reply-To: <a697e8c8-89f9-b059-6217-688536cb17ab@gmail.com>
On Tue, 27 Jun 2023 16:12:05 PDT (-0700), jeffreyalaw@gmail.com wrote:
>
>
> On 6/27/23 08:32, Philipp Tomsich wrote:
>> Thanks for taking care of this.
>> I had v2 in the queue for this week—even better if it took care of itself.
> :-) Didn't seem to be any value in waiting given its state and the
> release branch being cut next week.
>
>
>>
>> The updated GCC patches should go out right after the final
>> (incorporating comments from the public review) specification goes out.
> Sounds good.
>
> Per a discussion earlier today, Zfa is frozen, so I think we're at a
> point where Zfa can move forward for binutils as well (thus paving the
> way for GCC to support Zfa). I was just looking at the V5 patch from
> Christoph and I don't see anything concerning in there. Raphael
> double-checked the MATCH/MASKs a month or so ago.
>
> Any objections to me pushing that forward in binutils?
It might be better to post on that patch? IIRC the only blocker left
for Zfa was <https://github.com/riscv-non-isa/riscv-asm-manual/pull/85>,
which is still open.
>
> jeff
next prev parent reply other threads:[~2023-06-27 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 0:29 Philipp Tomsich
2023-01-26 0:26 ` Jeff Law
2023-01-26 1:02 ` Andrew Waterman
2023-03-01 1:58 ` Nelson Chu
2023-03-01 2:03 ` Palmer Dabbelt
2023-06-19 14:21 ` Philipp Tomsich
2023-06-21 4:25 ` Jeff Law
2023-06-21 4:38 ` Palmer Dabbelt
2023-06-27 13:27 ` Jeff Law
2023-06-27 14:32 ` Philipp Tomsich
2023-06-27 23:12 ` Jeff Law
2023-06-27 23:33 ` Palmer Dabbelt [this message]
2023-06-27 14:48 ` Palmer Dabbelt
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=mhng-eb02047f-8515-4668-850a-a4e792e5fd40@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=binutils@sourceware.org \
--cc=christoph.muellner@vrull.eu \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=nelson@rivosinc.com \
--cc=philipp.tomsich@vrull.eu \
/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).