From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Nelson Chu <nelson@rivosinc.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] RISC-V: Update ratified 'Ztso' extension version
Date: Tue, 8 Aug 2023 14:28:02 +0900 [thread overview]
Message-ID: <2df2e592-4f20-4c9e-8434-f21cde71df1a@irq.a4lg.com> (raw)
In-Reply-To: <CAPpQWtCD4E3BnTPbo3DfXf4qtqQkLLbh-Nyp-t2DfNYuLO5K+w@mail.gmail.com>
Appreciate that and committed.
Thanks,
Tsukasa
On 2023/08/08 14:22, Nelson Chu wrote:
> Okay, thanks.
>
> Nelson
>
> On Tue, Aug 8, 2023 at 12:36 PM 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>>
>
> Because the 'Ztso' extension is now ratified, it has a version
> number of 1.0
> (not 0.1). This commit updates the number.
>
> bfd/ChangeLog:
>
> * elfxx-riscv.c (riscv_supported_std_z_ext): Update the version
> number of the 'Ztso' extension since it's ratified.
> ---
> bfd/elfxx-riscv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/bfd/elfxx-riscv.c b/bfd/elfxx-riscv.c
> index ee4598729480..bc0c68940a67 100644
> --- a/bfd/elfxx-riscv.c
> +++ b/bfd/elfxx-riscv.c
> @@ -1317,7 +1317,7 @@ static struct riscv_supported_ext
> riscv_supported_std_z_ext[] =
> {"zvl16384b", ISA_SPEC_CLASS_DRAFT, 1,
> 0, 0 },
> {"zvl32768b", ISA_SPEC_CLASS_DRAFT, 1,
> 0, 0 },
> {"zvl65536b", ISA_SPEC_CLASS_DRAFT, 1,
> 0, 0 },
> - {"ztso", ISA_SPEC_CLASS_DRAFT, 0, 1, 0 },
> + {"ztso", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zca", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zcb", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zcf", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
>
> base-commit: d734d43a048b33ee12df2c06c2e782887e9715f6
> --
> 2.41.0
>
prev parent reply other threads:[~2023-08-08 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 4:36 Tsukasa OI
2023-08-08 5:22 ` Nelson Chu
2023-08-08 5:28 ` 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=2df2e592-4f20-4c9e-8434-f21cde71df1a@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--cc=nelson@rivosinc.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).