From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Nelson Chu <nelson@rivosinc.com>, Palmer Dabbelt <palmer@dabbelt.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] RISC-V: Remove support for non-existing 'Zve32d'
Date: Fri, 11 Aug 2023 11:00:30 +0900 [thread overview]
Message-ID: <ccd4845b-bd18-4244-ad94-b9f171a23941@irq.a4lg.com> (raw)
In-Reply-To: <CAPpQWtDQ+8B=d2KFngx=W-ABDqBN40+q-tLmKSc-OKWi-T_k-Q@mail.gmail.com>
On 2023/08/11 9:38, Nelson Chu wrote:
> Okay, seems it's just a
> typo, https://github.com/riscv/riscv-v-spec/commit/3af89ab16dd0ea85b15db35a2cd3c94aae5859a5 <https://github.com/riscv/riscv-v-spec/commit/3af89ab16dd0ea85b15db35a2cd3c94aae5859a5>.
Oh, that was also a very "close-to-ratified-1.0" change.
On 2023/08/11 10:51, Palmer Dabbelt wrote:
> Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
Thanks you two for reviewing! Committed.
Thanks,
Tsukasa
>
> Thanks
> Nelson
>
> On Thu, Aug 3, 2023 at 9:19 AM Tsukasa OI <research_trasio@irq.a4lg.com
> <mailto:research_trasio@irq.a4lg.com>> wrote:
>
> From: Tsukasa OI <research_trasio@irq.a4lg.com
> <mailto:research_trasio@irq.a4lg.com>>
>
> Since this "extension" does not exist (on the other hand, 'Zve64d'
> exists)
> and it's not useful if we keep it (as other code portions just ignore
> "zve32d"), this commit just removes it.
>
> bfd/ChangeLog:
>
> * elfxx-riscv.c (riscv_supported_std_z_ext): Remove 'Zve32d'
> extension from the list.
> ---
> bfd/elfxx-riscv.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/bfd/elfxx-riscv.c b/bfd/elfxx-riscv.c
> index ba5165766b2b..1971e6ba6a6b 100644
> --- a/bfd/elfxx-riscv.c
> +++ b/bfd/elfxx-riscv.c
> @@ -1280,7 +1280,6 @@ static struct riscv_supported_ext
> riscv_supported_std_z_ext[] =
> {"zkt", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zve32x", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zve32f", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> - {"zve32d", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zve64x", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zve64f", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zve64d", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
>
> base-commit: 4b177a76d5b759ba631568fb69e8750e99b43647
> --
> 2.41.0
>
prev parent reply other threads:[~2023-08-11 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 1:19 Tsukasa OI
2023-08-09 23:37 ` Tsukasa OI
2023-08-11 0:38 ` Nelson Chu
2023-08-11 1:51 ` Palmer Dabbelt
2023-08-11 2:00 ` 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=ccd4845b-bd18-4244-ad94-b9f171a23941@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--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).