From: shihua@iscas.ac.cn
To: "Tsukasa OI" <research_trasio@irq.a4lg.com>
Cc: "Nelson Chu" <nelson@rivosinc.com>, binutils@sourceware.org
Subject: Re: [PATCH 0/1] RISC-V: Minor fix to the 'Ztso' extension support
Date: Wed, 21 Sep 2022 17:53:40 +0800 (GMT+08:00) [thread overview]
Message-ID: <5f6cebd7.98e3.1835f77a59d.Coremail.shihua@iscas.ac.cn> (raw)
In-Reply-To: <cover.1663742326.git.research_trasio@irq.a4lg.com>
Hi,Tsukasa OI
In patch V4 ( https://sourceware.org/pipermail/binutils/2022-September/122962.html ), I removed support tso for the .option directive. So I think it's not necessary to add this.
Thanks，
Shihua
> -----原始邮件-----
> 发件人: "Tsukasa OI" <research_trasio@irq.a4lg.com>
> 发送时间: 2022-09-21 14:40:42 (星期三)
> 收件人: "Tsukasa OI" <research_trasio@irq.a4lg.com>, "Nelson Chu" <nelson@rivosinc.com>, "Shihua LIAO" <shihua@iscas.ac.cn>
> 抄送: binutils@sourceware.org
> 主题: [PATCH 0/1] RISC-V: Minor fix to the 'Ztso' extension support
>
> Hi all,
>
> I think Shihua could have missed my review 2:
> <https: sourceware.org="" pipermail="" binutils="" 2022-september="" 122916.html="">
> (see near the end of my e-mail starting with "Other than that,").
>
> Currently, it sets EF_RISCV_TSO ELF flag when initial ISA string contains
> the 'Ztso' extension. However, GAS has a way to update the ISA string:
> ".option arch".
>
> When the architecture is updated by ".option arch", EF_RISCV_RVC ELF flag
> is set when the 'C' extension is detected. Analogously, this patchset sets
> the EF_RISCV_TSO when the 'Ztso' extension is detected.
>
> With this patch, the 'Ztso' extension support will be complete.
>
> Thanks,
>
>
>
>
> Tsukasa OI (1):
> RISC-V: Set EF_RISCV_TSO also on .option arch
>
> gas/config/tc-riscv.c | 3 +++
> 1 file changed, 3 insertions(+)
>
>
> base-commit: e472ec9fad6d7b0da914da606430e249d1bd99e4
> --
> 2.34.1
</https:></shihua@iscas.ac.cn></nelson@rivosinc.com></research_trasio@irq.a4lg.com></research_trasio@irq.a4lg.com>
next prev parent reply other threads:[~2022-09-21 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 9:45 [PATCH V4] RISC-V: Implement Ztso extension shihua
2022-09-21 3:47 ` Nelson Chu
2022-09-21 6:40 ` [PATCH 0/1] RISC-V: Minor fix to the 'Ztso' extension support Tsukasa OI
2022-09-21 6:40 ` [PATCH 1/1] RISC-V: Set EF_RISCV_TSO also on .option arch Tsukasa OI
2022-09-21 7:24 ` Nelson Chu
2022-09-21 9:53 ` shihua [this message]
2022-09-21 10:14 ` [PATCH 0/1] RISC-V: Minor fix to the 'Ztso' extension support Tsukasa OI
2022-09-21 10:21 ` shihua
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=5f6cebd7.98e3.1835f77a59d.Coremail.shihua@iscas.ac.cn \
--to=shihua@iscas.ac.cn \
--cc=binutils@sourceware.org \
--cc=nelson@rivosinc.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).