From: Nelson Chu <nelson@rivosinc.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Kito Cheng <kito.cheng@sifive.com>,
binutils@sourceware.org
Subject: Re: [PATCH] RISC-V: Update ratified 'Ztso' extension version
Date: Tue, 8 Aug 2023 13:22:16 +0800 [thread overview]
Message-ID: <CAPpQWtCD4E3BnTPbo3DfXf4qtqQkLLbh-Nyp-t2DfNYuLO5K+w@mail.gmail.com> (raw)
In-Reply-To: <e3f5898021ba21d9ad855b325cef92019a17b04d.1691469367.git.research_trasio@irq.a4lg.com>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
Okay, thanks.
Nelson
On Tue, Aug 8, 2023 at 12:36 PM Tsukasa OI <research_trasio@irq.a4lg.com>
wrote:
> From: Tsukasa OI <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
>
>
next prev parent reply other threads:[~2023-08-08 5:22 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 [this message]
2023-08-08 5:28 ` 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=CAPpQWtCD4E3BnTPbo3DfXf4qtqQkLLbh-Nyp-t2DfNYuLO5K+w@mail.gmail.com \
--to=nelson@rivosinc.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=jim.wilson.gcc@gmail.com \
--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).