public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Kito Cheng <kito.cheng@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Nelson Chu <nelson.chu@sifive.com>
Cc: Binutils <binutils@sourceware.org>
Subject: [PING][PATCH] RISC-V: Update Zihintpause extension version
Date: Tue, 24 May 2022 18:44:08 +0900	[thread overview]
Message-ID: <3f11f3f2-a83b-2588-623b-22cc0d1cbf33@irq.a4lg.com> (raw)
In-Reply-To: <c55a167d9eb1139209963ee62579bc08fdcd1308.1643542620.git.research_trasio@irq.a4lg.com>

On 2022/01/30 20:37, Tsukasa OI 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 9f52bb545ac..29755a6cb0a 100644
> --- a/bfd/elfxx-riscv.c
> +++ b/bfd/elfxx-riscv.c
> @@ -1183,7 +1183,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 },
>    {"zfinx",		ISA_SPEC_CLASS_DRAFT,		1, 0,  0 },
>    {"zdinx",		ISA_SPEC_CLASS_DRAFT,		1, 0,  0 },
>    {"zqinx",		ISA_SPEC_CLASS_DRAFT,		1, 0,  0 },
> 
> base-commit: 35b5767cf47169d11aa059fce0ed5b0fc213045d

Let me allow to send a ping.

Original:
https://sourceware.org/pipermail/binutils/2022-January/119545.html
Some discussion:
https://sourceware.org/pipermail/binutils/2022-February/119588.html

I completely understand that my other fixes (except this and RV32Q) are
relatively large and needs some time to review.

I think this (and RV32Q patch) are completely safe to merge.

Thanks,
Tsukasa

      parent reply	other threads:[~2022-05-24  9:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30 11:37 [PATCH] " Tsukasa OI
2022-01-31 16:44 ` Palmer Dabbelt
2022-02-01  2:20   ` Andrew Waterman
2022-02-01 13:46     ` Tsukasa OI
2022-02-02  0:12       ` Palmer Dabbelt
2022-02-02  0:36         ` Tsukasa OI
2022-02-02  1:03         ` Hans-Peter Nilsson
2022-05-24  9:44 ` 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=3f11f3f2-a83b-2588-623b-22cc0d1cbf33@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=binutils@sourceware.org \
    --cc=kito.cheng@sifive.com \
    --cc=nelson.chu@sifive.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).