From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Greg Favor <gfavor@ventanamicro.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Nelson Chu <nelson@rivosinc.com>,
Kito Cheng <kito.cheng@sifive.com>,
Jeff Law <jlaw@ventanamicro.com>,
binutils@sourceware.org
Subject: Re: [PATCH 0/1] RISC-V: Make XVentanaCondOps RV64 only
Date: Wed, 30 Aug 2023 12:59:55 +0900 [thread overview]
Message-ID: <91a98bd8-662c-4153-9113-69f67984e1c3@irq.a4lg.com> (raw)
In-Reply-To: <CA+Qh7Tn7kHAEML_ibkKHk_UmXengY9p2pPD6M2qhJZ994e-iiw@mail.gmail.com>
On 2023/08/30 12:21, Greg Favor wrote:
> On Tue, Aug 29, 2023 at 6:38 PM Tsukasa OI <research_trasio@irq.a4lg.com
> <mailto:research_trasio@irq.a4lg.com>> wrote:
>
> Unless Ventana is working on some RV32 processors (and soon to be
> released
> ), I think disabling XVentanaCondOps instructions on RV32 would be safer
> (to prevent possible misuses). I would like to hear thoughts especially
> from Ventana employees since I am just a volunteer.
>
>
> Representing Ventana, what you say is correct, i.e. we have no plans to
> do RV32 processors.
>
> Greg
Thanks for the official information. Committing.
(we could make XVentanaCondOps invalid on RV32 considering your answer
but that's for another time.)
Tsukasa
>
>
> I also chose not to reject XVentanaCondOps + RV32 because it is not
> stated
> that is illegal (unlike Zcf + RV64). This patch set makes
> XVentanaCondOps
> + RV32 empty (yet legal).
>
prev parent reply other threads:[~2023-08-30 3:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 1:38 Tsukasa OI
2023-08-30 1:38 ` [PATCH 1/1] " Tsukasa OI
2023-08-30 2:45 ` Nelson Chu
2023-08-30 2:48 ` Tsukasa OI
2023-08-30 3:21 ` [PATCH 0/1] " Greg Favor
2023-08-30 3:59 ` Tsukasa OI [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=91a98bd8-662c-4153-9113-69f67984e1c3@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=gfavor@ventanamicro.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=jlaw@ventanamicro.com \
--cc=kito.cheng@sifive.com \
--cc=nelson@rivosinc.com \
--cc=palmer@dabbelt.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).