From: Vineet Gupta <vineetg@rivosinc.com>
To: Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: kito.cheng@gmail.com, Jeff Law <jeffreyalaw@gmail.com>,
Palmer Dabbelt <palmer@rivosinc.com>
Subject: Re: [PATCH 1/2] riscv: zicond: make non-experimental
Date: Tue, 8 Aug 2023 11:45:49 -0700 [thread overview]
Message-ID: <9fceb378-f079-e9ff-b8fe-da05b51fc1e1@rivosinc.com> (raw)
In-Reply-To: <0938f9c9-98a4-7238-c644-3eebd8964f87@linaro.org>
On 8/8/23 11:29, Richard Henderson wrote:
> On 8/8/23 11:17, Vineet Gupta wrote:
>> zicond is now codegen supported in both llvm and gcc.
>
> It is still not in
>
> https://wiki.riscv.org/display/HOME/Recently+Ratified+Extensions
Right, its been frozen since April though and with support trickling in
rest of tooling it becomes harder to test.
I don't know what exactly QEMU's policy is on this ?
-Vineet
next prev parent reply other threads:[~2023-08-08 18:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 18:17 [PATCH 1/2] riscv: zicond: make non-experimental Vineet Gupta
2023-08-08 18:17 ` [PATCH 2/2] riscv: zicond: make default Vineet Gupta
2023-08-08 21:06 ` Daniel Henrique Barboza
2023-08-08 22:10 ` Vineet Gupta
2023-08-10 18:07 ` Alistair Francis
2023-08-11 7:01 ` Andrew Jones
2023-10-16 5:39 ` Alistair Francis
2023-10-16 7:43 ` Andrew Jones
2023-08-11 11:22 ` Daniel Henrique Barboza
2023-08-08 18:29 ` [PATCH 1/2] riscv: zicond: make non-experimental Richard Henderson
2023-08-08 18:45 ` Vineet Gupta [this message]
2023-08-08 20:52 ` Palmer Dabbelt
2023-08-08 21:10 ` Daniel Henrique Barboza
2023-08-08 21:15 ` Palmer Dabbelt
2023-08-10 17:13 ` Alistair Francis
2023-08-10 17:14 ` Alistair Francis
2023-08-25 5:28 ` Vineet Gupta
2023-09-01 2:20 ` Alistair Francis
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=9fceb378-f079-e9ff-b8fe-da05b51fc1e1@rivosinc.com \
--to=vineetg@rivosinc.com \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.org \
/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 NNTP newsgroup(s).