public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nelson Chu <nelson@rivosinc.com>
To: jiawei@iscas.ac.cn
Cc: Tsukasa OI <research_trasio@irq.a4lg.com>,
	 "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH] RISC-V: Add actual 'Zvkt' extension support
Date: Fri, 28 Jul 2023 11:44:15 +0800	[thread overview]
Message-ID: <CAPpQWtBLFZVb88Z0PwzBQNeWgtut=DDruwuG_HU-ddmk-EXMVg@mail.gmail.com> (raw)
In-Reply-To: <4d6c4075.28fac.18995ac1c5a.Coremail.jiawei@iscas.ac.cn>

[-- Attachment #1: Type: text/plain, Size: 2400 bytes --]

Ok, thanks, please commit.

Nelson

On Thu, Jul 27, 2023 at 12:47 PM <jiawei@iscas.ac.cn> wrote:

> LGMT, thanks for this work.
>
> > From: Tsukasa OI <research_trasio@irq.a4lg.com>
> >
> > The 'Zvkt' extension is listed on the added extensions in the GNU
> Binutils
> > version 2.41 (see binutils/NEWS).  However, the support of this extension
> > was actually missing.
> >
> > This commit adds actual support of this extension and adds implications
> > from 'Zvkn' and 'Zvks' superset extensions.
> >
> > bfd/ChangeLog:
> >
> > * elfxx-riscv.c (riscv_implicit_subsets) Add implications from
> > 'Zvkn' and 'Zvks'.  (riscv_supported_std_z_ext): Add 'Zvkt' to
> > the supported extension list.
> > ---
> >  bfd/elfxx-riscv.c | 3 +++
> >  1 file changed, 3 insertions(+)
> >
> > diff --git a/bfd/elfxx-riscv.c b/bfd/elfxx-riscv.c
> > index b43d2cfa0fab..ba5165766b2b 100644
> > --- a/bfd/elfxx-riscv.c
> > +++ b/bfd/elfxx-riscv.c
> > @@ -1162,6 +1162,7 @@ static struct riscv_implicit_subset
> riscv_implicit_subsets[] =
> >    {"zvkn", "zvknha", check_implicit_always},
> >    {"zvkn", "zvknhb", check_implicit_always},
> >    {"zvkn", "zvbb", check_implicit_always},
> > +  {"zvkn", "zvkt", check_implicit_always},
> >    {"zvkng", "zvkn", check_implicit_always},
> >    {"zvkng", "zvkg", check_implicit_always},
> >    {"zvknc", "zvkn", check_implicit_always},
> > @@ -1169,6 +1170,7 @@ static struct riscv_implicit_subset
> riscv_implicit_subsets[] =
> >    {"zvks", "zvksed", check_implicit_always},
> >    {"zvks", "zvksh", check_implicit_always},
> >    {"zvks", "zvbb", check_implicit_always},
> > +  {"zvks", "zvkt", check_implicit_always},
> >    {"zvksg", "zvks", check_implicit_always},
> >    {"zvksg", "zvkg", check_implicit_always},
> >    {"zvksc", "zvks", check_implicit_always},
> > @@ -1296,6 +1298,7 @@ static struct riscv_supported_ext
> riscv_supported_std_z_ext[] =
> >    {"zvks", ISA_SPEC_CLASS_DRAFT, 1, 0,  0 },
> >    {"zvksg", ISA_SPEC_CLASS_DRAFT, 1, 0,  0 },
> >    {"zvksc", ISA_SPEC_CLASS_DRAFT, 1, 0,  0 },
> > +  {"zvkt", ISA_SPEC_CLASS_DRAFT, 1, 0,  0 },
> >    {"zvl32b", ISA_SPEC_CLASS_DRAFT, 1, 0,  0 },
> >    {"zvl64b", ISA_SPEC_CLASS_DRAFT, 1, 0,  0 },
> >    {"zvl128b", ISA_SPEC_CLASS_DRAFT, 1, 0,  0 },
> >
> > base-commit: 477c9f2ba26ccd77016f2c97941fc8b35e332e35
> > --
> > 2.41.0
>
>
>

  reply	other threads:[~2023-07-28  3:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  4:47 jiawei
2023-07-28  3:44 ` Nelson Chu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-26  1:51 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='CAPpQWtBLFZVb88Z0PwzBQNeWgtut=DDruwuG_HU-ddmk-EXMVg@mail.gmail.com' \
    --to=nelson@rivosinc.com \
    --cc=binutils@sourceware.org \
    --cc=jiawei@iscas.ac.cn \
    --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).