From: jiawei@iscas.ac.cn
To: "Jan Beulich" <jbeulich@suse.com>
Cc: nelson@rivosinc.com, kito.cheng@sifive.com, palmer@dabbelt.com,
research_trasio@irq.a4lg.com, christoph.muellner@vrull.eu,
jeremy.bennett@embecosm.com, wuwei2016@iscas.ac.cn,
shihua@iscas.ac.cn, shiyulong@iscas.ac.cn,
chenyixuan@iscas.ac.cn, binutils@sourceware.org
Subject: Re: Re: [PATCH] RISC-V: Support Zabha extension.
Date: Wed, 28 Feb 2024 16:29:09 +0800 (GMT+08:00) [thread overview]
Message-ID: <5de8e2b1.1d9b9.18deed4f2ec.Coremail.jiawei@iscas.ac.cn> (raw)
In-Reply-To: <4da6f461-f86e-4662-b994-c7f41f91c17a@suse.com>
> -----原始邮件-----
> 发件人: "Jan Beulich" <jbeulich@suse.com>
> 发送时间: 2024-02-28 15:53:46 (星期三)
> 收件人: Jiawei <jiawei@iscas.ac.cn>
> 抄送: nelson@rivosinc.com, kito.cheng@sifive.com, palmer@dabbelt.com, research_trasio@irq.a4lg.com, christoph.muellner@vrull.eu, jeremy.bennett@embecosm.com, wuwei2016@iscas.ac.cn, shihua@iscas.ac.cn, shiyulong@iscas.ac.cn, chenyixuan@iscas.ac.cn, binutils@sourceware.org
> 主题: Re: [PATCH] RISC-V: Support Zabha extension.
>
> On 28.02.2024 07:41, Jiawei wrote:
> > --- a/bfd/elfxx-riscv.c
> > +++ b/bfd/elfxx-riscv.c
> > @@ -1274,6 +1274,7 @@ static struct riscv_supported_ext riscv_supported_std_z_ext[] =
> > {"zihintpause", ISA_SPEC_CLASS_DRAFT, 2, 0, 0 },
> > {"zihpm", ISA_SPEC_CLASS_DRAFT, 2, 0, 0 },
> > {"zmmul", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> > + {"zabha", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> > {"zawrs", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> > {"zfa", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
> > {"zfh", ISA_SPEC_CLASS_DRAFT, 1, 0, 0 },
>
> Yet higher up in the file there's riscv_implicit_subsets[], which I
> think also needs a new line added, to make a connection to the A
> extension.
>
> Jan
Thanks for your suggestion, I update the imply relation that "Zabha -> A" in the new patch:
https://sourceware.org/pipermail/binutils/2024-February/132707.html
Jiawei</jiawei@iscas.ac.cn></jbeulich@suse.com>
prev parent reply other threads:[~2024-02-28 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 6:41 Jiawei
2024-02-28 7:53 ` Jan Beulich
2024-02-28 8:29 ` jiawei [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=5de8e2b1.1d9b9.18deed4f2ec.Coremail.jiawei@iscas.ac.cn \
--to=jiawei@iscas.ac.cn \
--cc=binutils@sourceware.org \
--cc=chenyixuan@iscas.ac.cn \
--cc=christoph.muellner@vrull.eu \
--cc=jbeulich@suse.com \
--cc=jeremy.bennett@embecosm.com \
--cc=kito.cheng@sifive.com \
--cc=nelson@rivosinc.com \
--cc=palmer@dabbelt.com \
--cc=research_trasio@irq.a4lg.com \
--cc=shihua@iscas.ac.cn \
--cc=shiyulong@iscas.ac.cn \
--cc=wuwei2016@iscas.ac.cn \
/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).