From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Nelson Chu <nelson@rivosinc.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 0/1] RISC-V: Handle 'Zca' extension on ".option arch"
Date: Tue, 25 Jul 2023 11:23:58 +0900 [thread overview]
Message-ID: <700f10ff-a66e-1cfa-e293-12e955bca07d@irq.a4lg.com> (raw)
In-Reply-To: <CAPpQWtAZUV+0OpnYuGFbZ6awttR=K4yb11K2O_wjZ=ymTdMHZA@mail.gmail.com>
On 2023/07/25 11:21, Nelson Chu wrote:
> Thanks, I did forget this, it looks good.
>
> Nelson
Thanks, committing.
Best,
Tsukasa
>
> On Tue, Jul 25, 2023 at 9:56 AM Tsukasa OI <research_trasio@irq.a4lg.com
> <mailto:research_trasio@irq.a4lg.com>> wrote:
>
> Hi,
>
> While I'm testing the PATCH v2 of the 'Zihintntl', I found a bug in GAS.
>
> (Normally I wouldn't attach a cover letter for the patch set that
> simple,
> I felt it's needed for a little context; PATCH v2 of 'Zihintntl'
> will need
> this bug fix.)
>
> While the 'Zca' extension is the new base for compressed instructions,
> it was not correctly handled in the ".option arch" handling. This patch
> set fixes this issue. After grepping "c", I think it's the last code to
> test.
>
> Thanks,
> Tsukasa
>
>
>
>
> Tsukasa OI (1):
> RISC-V: Enable RVC on ".option arch, +zca" etc.
>
> gas/config/tc-riscv.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
>
> base-commit: 3dfee72010248aca5932a27b4c34d3b79ab9f057
> --
> 2.41.0
>
prev parent reply other threads:[~2023-07-25 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 1:56 Tsukasa OI
2023-07-25 1:56 ` [PATCH 1/1] RISC-V: Enable RVC on ".option arch, +zca" etc Tsukasa OI
2023-07-25 2:21 ` [PATCH 0/1] RISC-V: Handle 'Zca' extension on ".option arch" Nelson Chu
2023-07-25 2:23 ` 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=700f10ff-a66e-1cfa-e293-12e955bca07d@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--cc=nelson@rivosinc.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).