From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Binutils <binutils@sourceware.org>
Subject: Re: [REVIEW ONLY v2 0/1] UNRATIFIED RISC-V: Add 'ZiCondOps' extension (encodings changed!)
Date: Tue, 29 Nov 2022 11:40:12 +0900 [thread overview]
Message-ID: <70bdf9b2-4705-856e-6b35-07c152ea6b8c@irq.a4lg.com> (raw)
In-Reply-To: <cover.1669687611.git.research_trasio@irq.a4lg.com>
IMPORTANT NOTE:
I just received an e-mail from Andrew.
Considering his statements...
1. Actual encodings will change **again** and
2. The extension name is going to be 'Zicond', not 'Zicondops'.
I'll submit PATCH v3 after both are reflected.
Regards,
Tsukasa
On 2022/11/29 11:06, Tsukasa OI wrote:
> *** WAIT FOR SPECIFICATION FREEZE ***
> This is an implementation for unratified and not frozen RISC-V extension
> and not intended to be merged for now.
> The only intent to submit this patchset is to test new instructions for
> your (possibly virtual) environment and early review for fast adoption
> after ratification.
>
>
> Just two hours ago, the encodings of "czero.eqz" and "czero.nez"
> instructions have changed in the commit 8c5faf4c6d73.
>
> This PATCH v2 reflects this change.
>
>
> This patchset adds following unratified extension to GNU Binutils:
>
> - 'ZiCondOps' (Integer Conditional Operations)
> version 1.0 in development
>
> which adds 2 instructions ("czero.eqz" and "czero.nez").
>
> This extension makes conditional arithmetic feature much simpler (fewer
> instructions when no branches are allowed). Note that constant timing
> guarantee (data-independence / certain side-channel resistance) for this
> extension is being discussed and may not be guaranteed.
>
>
> This is based on the commit 8c5faf4c6d73 of the specification document:
> <https://github.com/riscv/riscv-zicondops>
>
>
>
>
> Tsukasa OI (1):
> UNRATIFIED RISC-V: Add 'ZiCondOps' extension
>
> bfd/elfxx-riscv.c | 5 +++++
> gas/testsuite/gas/riscv/zicondops-noarch.d | 3 +++
> gas/testsuite/gas/riscv/zicondops-noarch.l | 3 +++
> gas/testsuite/gas/riscv/zicondops.d | 11 +++++++++++
> gas/testsuite/gas/riscv/zicondops.s | 3 +++
> include/opcode/riscv-opc.h | 8 ++++++++
> include/opcode/riscv.h | 1 +
> opcodes/riscv-opc.c | 4 ++++
> 8 files changed, 38 insertions(+)
> create mode 100644 gas/testsuite/gas/riscv/zicondops-noarch.d
> create mode 100644 gas/testsuite/gas/riscv/zicondops-noarch.l
> create mode 100644 gas/testsuite/gas/riscv/zicondops.d
> create mode 100644 gas/testsuite/gas/riscv/zicondops.s
>
>
> base-commit: cb44f89ce977b1ab2d4063f2487950bddfb75bc7
next prev parent reply other threads:[~2022-11-29 2:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 1:16 [REVIEW ONLY 0/1] UNRATIFIED RISC-V: Add 'ZiCondOps' extension Tsukasa OI
2022-11-29 1:16 ` [REVIEW ONLY 1/1] " Tsukasa OI
2022-11-29 1:41 ` Palmer Dabbelt
2022-11-29 2:19 ` Tsukasa OI
2022-11-29 2:38 ` Palmer Dabbelt
2022-11-29 2:06 ` [REVIEW ONLY v2 0/1] UNRATIFIED RISC-V: Add 'ZiCondOps' extension (encodings changed!) Tsukasa OI
2022-11-29 2:06 ` [REVIEW ONLY v2 1/1] UNRATIFIED RISC-V: Add 'ZiCondOps' extension Tsukasa OI
2022-11-29 2:40 ` Tsukasa OI [this message]
2022-12-01 3:20 ` [REVIEW ONLY v3 0/1] UNRATIFIED RISC-V: Add 'ZiCond' extension Tsukasa OI
2022-12-01 3:20 ` [REVIEW ONLY v3 1/1] " Tsukasa OI
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=70bdf9b2-4705-856e-6b35-07c152ea6b8c@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).