From: Jan Beulich <jbeulich@suse.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Nelson Chu <nelson.chu@sifive.com>
Cc: binutils@sourceware.org, Kito Cheng <kito.cheng@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [RESEND PATCH 1/1] RISC-V: Update Zihintpause extension version
Date: Mon, 4 Jul 2022 08:26:10 +0200 [thread overview]
Message-ID: <1f0109c8-45fd-ef96-1f2a-d51dacbf2887@suse.com> (raw)
In-Reply-To: <01295176a63d702b1a8c929d8ad2e1ae4a677516.1656844281.git.research_trasio@irq.a4lg.com>
On 03.07.2022 12:31, Tsukasa OI via Binutils wrote:
> Because ratified Zihintpause extension has a version number of 2.0
> (not 1.0), we should update the number.
>
> bfd/ChangeLog:
>
> * elfxx-riscv.c (riscv_supported_std_z_ext): Update version
> number of Zihintpause extension.
> ---
> 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 bf7dc20e892..c846d6baaa2 100644
> --- a/bfd/elfxx-riscv.c
> +++ b/bfd/elfxx-riscv.c
> @@ -1185,7 +1185,7 @@ static struct riscv_supported_ext riscv_supported_std_z_ext[] =
> {"zicsr", ISA_SPEC_CLASS_20190608, 2, 0, 0 },
> {"zifencei", ISA_SPEC_CLASS_20191213, 2, 0, 0 },
> {"zifencei", ISA_SPEC_CLASS_20190608, 2, 0, 0 },
> - {"zihintpause", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> + {"zihintpause", ISA_SPEC_CLASS_DRAFT, 2, 0, 0 },
> {"zfh", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zfinx", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> {"zdinx", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
Just for my own education: Isn't the general versioning scheme using
2.x only for non-draft functionality?
Jan
next prev parent reply other threads:[~2022-07-04 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 10:31 [RESEND PATCH 0/1] RISC-V: Update 'Zihintpause' " Tsukasa OI
2022-07-03 10:31 ` [RESEND PATCH 1/1] RISC-V: Update Zihintpause " Tsukasa OI
2022-07-04 1:37 ` Nelson Chu
2022-07-04 6:26 ` Jan Beulich [this message]
2022-07-05 10:40 ` Kito Cheng
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=1f0109c8-45fd-ef96-1f2a-d51dacbf2887@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=kito.cheng@sifive.com \
--cc=nelson.chu@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).