From: Andrew Waterman <andrew@sifive.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] RISC-V: Update Zihintpause extension version
Date: Mon, 31 Jan 2022 18:20:49 -0800 [thread overview]
Message-ID: <CA++6G0AnzhuGdVxQaG4ooiTe6oEAM0jgJC2e=SWR-Mrw5s7o7g@mail.gmail.com> (raw)
In-Reply-To: <mhng-162ac599-e4c0-48be-84c6-97d53b351ac6@palmer-ri-x1c9>
On Mon, Jan 31, 2022 at 8:45 AM Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> On Sun, 30 Jan 2022 03:37:41 PST (-0800), binutils@sourceware.org wrote:
> > Because ratified Zihintpause extension has a version number of 2.0
> > (not 1.0), we should update the number.
>
> The ISA manual also says it's ratified so having it in the draft set is
> kind of odd, but I'm not sure which spec version it should be included
> in. The commits saying it was ratified are in August 2021, but I can't
> find a spec version that's listed as ratified and contains the new 2.0
> (there was also an earlier 2.0, from before the 1.0).
>
> Not sure if this matters, though. Looks like the only non-commentary
> differents are: from the original 2.0 to 1.0, the text "No architectural
> state is changed." was added; and from 1.0 to 2.0 the text "{\em fm}=0,
> {\em rd}={\tt x0}, and {\em rs1}={\tt x0}" was added (to the encoding
> section). The second one isn't substantive, and while the first one
> reads like a change to me IIRC we've been through that before and I just
> have the definition of architectural state change wrong.
The first one isn't substantive, either, because of the definition of
HINT. It's just a clarification.
>
> >
> > 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
next prev parent reply other threads:[~2022-02-01 2:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 11:37 Tsukasa OI
2022-01-31 16:44 ` Palmer Dabbelt
2022-02-01 2:20 ` Andrew Waterman [this message]
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 ` [PING][PATCH] " 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='CA++6G0AnzhuGdVxQaG4ooiTe6oEAM0jgJC2e=SWR-Mrw5s7o7g@mail.gmail.com' \
--to=andrew@sifive.com \
--cc=binutils@sourceware.org \
--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).