From: Nelson Chu <nelson@rivosinc.com>
To: Xiao Zeng <zengxiao@eswincomputing.com>
Cc: binutils@sourceware.org, kito.cheng@gmail.com, palmer@dabbelt.com
Subject: Re: [PATCH] RISC-V: Update 'Zfa' extension version
Date: Fri, 24 Nov 2023 15:54:26 +0800 [thread overview]
Message-ID: <CAPpQWtAYYvKS+GCJU_UF0BstKqyJr2xxO9sc_GD9Rjtwyay1+A@mail.gmail.com> (raw)
In-Reply-To: <20231121061121.1174-1-zengxiao@eswincomputing.com>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
Okay, committed, thanks.
Nelson
On Tue, Nov 21, 2023 at 2:11 PM Xiao Zeng <zengxiao@eswincomputing.com>
wrote:
> From: zengxiao <zengxiao@eswincomputing.com>
>
> Because the 'Zfa' extension 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 'Zfa' 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 c9acf124626..9ea70608504 100644
> --- a/bfd/elfxx-riscv.c
> +++ b/bfd/elfxx-riscv.c
> @@ -1268,7 +1268,7 @@ static struct riscv_supported_ext
> riscv_supported_std_z_ext[] =
> {"zihintpause", ISA_SPEC_CLASS_DRAFT, 2, 0, 0 },
> {"zmmul", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zawrs", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> - {"zfa", ISA_SPEC_CLASS_DRAFT, 0, 1, 0 },
> + {"zfa", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zfh", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zfhmin", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zfinx", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> --
> 2.17.1
>
>
next prev parent reply other threads:[~2023-11-24 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 6:11 Xiao Zeng
2023-11-24 7:54 ` Nelson Chu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-21 6:11 Xiao Zeng
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=CAPpQWtAYYvKS+GCJU_UF0BstKqyJr2xxO9sc_GD9Rjtwyay1+A@mail.gmail.com \
--to=nelson@rivosinc.com \
--cc=binutils@sourceware.org \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=zengxiao@eswincomputing.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).