From: Nelson Chu <nelson@rivosinc.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: Kito Cheng <kito.cheng@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
binutils@sourceware.org
Subject: Re: [PATCH 0/2] RISC-V: Reflect v1.0.4-1 of the code size reduction spec
Date: Tue, 25 Jul 2023 07:22:52 +0800 [thread overview]
Message-ID: <CAPpQWtCrWnCM252v6ZY1-oAQJ+GS8=Votncgvp9O1mt=XJL_BA@mail.gmail.com> (raw)
In-Reply-To: <cover.1690177089.git.research_trasio@irq.a4lg.com>
[-- Attachment #1: Type: text/plain, Size: 1976 bytes --]
ok, please commit these, thanks.
Nelson
On Mon, Jul 24, 2023 at 1:39 PM Tsukasa OI <research_trasio@irq.a4lg.com>
wrote:
> Hello again,
>
> I am pleased to announce that I can contribute to GNU Binutils again!
>
>
> This is a follow-up patch set for the code size reduction specification
> by Jiawei et al. (partial support excluding those that conflict with
> 'Zcd').
>
> This is compliant with the initial ratified version but there is a new
> version of the specification including minor additions.
>
> cf: The version 1.0.4-1 of the specification
> <https://github.com/riscv/riscv-code-size-reduction/releases/tag/v1.0.4-1>
>
> 1. 'Zcf' is only allowed on RV32 (as no instruction exists on RV64/128).
> 2. 'Zcf' implies 'F' and 'Zcd' implies D.
>
> This patch set makes GNU Binutils compliant with the latest code size
> reduction specification (a subset where GNU Binutils has already
> implemented) except a minor issue: 'C' does not imply 'Zca', 'Zcd' and
> 'Zcf' (only on RV32). Note that this is a consequence from handling of the
> 'Zmmul' extension (a subset of 'M').
>
> Thanks,
> Tsukasa
>
>
>
>
> Tsukasa OI (2):
> RISC-V: Prohibit the 'Zcf' extension on RV64
> RISC-V: Implications from 'Zc[fd]' extensions
>
> bfd/elfxx-riscv.c | 9 +++++++++
> gas/testsuite/gas/riscv/march-fail-rv64i_zcf.d | 3 +++
> gas/testsuite/gas/riscv/march-fail-rv64i_zcf.l | 2 ++
> gas/testsuite/gas/riscv/march-imply-zcd.d | 6 ++++++
> gas/testsuite/gas/riscv/march-imply-zcf.d | 6 ++++++
> 5 files changed, 26 insertions(+)
> create mode 100644 gas/testsuite/gas/riscv/march-fail-rv64i_zcf.d
> create mode 100644 gas/testsuite/gas/riscv/march-fail-rv64i_zcf.l
> create mode 100644 gas/testsuite/gas/riscv/march-imply-zcd.d
> create mode 100644 gas/testsuite/gas/riscv/march-imply-zcf.d
>
>
> base-commit: 5cbe549257b0aed1b615714e74bb6a3f066f3253
> --
> 2.41.0
>
>
prev parent reply other threads:[~2023-07-24 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 5:38 Tsukasa OI
2023-07-24 5:38 ` [PATCH 1/2] RISC-V: Prohibit the 'Zcf' extension on RV64 Tsukasa OI
2023-07-24 5:38 ` [PATCH 2/2] RISC-V: Implications from 'Zc[fd]' extensions Tsukasa OI
2023-07-24 23:22 ` Nelson Chu [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='CAPpQWtCrWnCM252v6ZY1-oAQJ+GS8=Votncgvp9O1mt=XJL_BA@mail.gmail.com' \
--to=nelson@rivosinc.com \
--cc=binutils@sourceware.org \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
--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).