From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Nelson Chu <nelson@rivosinc.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH v3 0/3] RISC-V: Add ratified 'E' base ISA support with draft ABIs
Date: Mon, 25 Sep 2023 17:04:39 +0900 [thread overview]
Message-ID: <3515bb91-d607-420b-bc6b-e8084783d7df@irq.a4lg.com> (raw)
In-Reply-To: <CAPpQWtA11WV9aFfnW3f5Xzv_PnZFU7s1Fv7XmYNjJMdcWM1ygw@mail.gmail.com>
On 2023/09/25 12:07, Nelson Chu wrote:
>
>
> On Tue, Sep 5, 2023 at 5:08 PM Tsukasa OI <research_trasio@irq.a4lg.com
> <mailto:research_trasio@irq.a4lg.com>> wrote:
>
> Hi,
>
> PATCH v1 (only Binutils):
> <https://sourceware.org/pipermail/binutils/2023-July/128583.html
> <https://sourceware.org/pipermail/binutils/2023-July/128583.html>>
> PATCH v2 (Binutils+GDB):
> <https://sourceware.org/pipermail/binutils/2023-August/129314.html
> <https://sourceware.org/pipermail/binutils/2023-August/129314.html>>
>
> Changes: v1 -> v2
> - Added GDB support
>
> Changes: v2 -> v3
> - Rebased against the latest master
> (PATCH 1/3 related merge conflict is now resolved)
>
>
> Related Project:
> PATCH 1/3: Binutils
> PATCH 2/3: Binutils
>
>
> Looks good to me :-)
>
>
> PATCH 3/3: GDB
>
>
> I cannot approve anything about gdb, so this will need gdb experts to help.
>
> Thanks
> Nelson
>
Thanks, I understand that you cannot approve GDB part so it's okay.
I'll commit if GDB part is also approved or I confirm that not applying
PATCH 3/3 does not cause unnecessary effects to Binutils and GDB (in
this case, I'll commit only PATCH 1-2/3).
Tsukasa
next prev parent reply other threads:[~2023-09-25 8:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 2:26 [PATCH 0/2] " Tsukasa OI
2023-07-25 2:26 ` [PATCH 1/2] RISC-V: Remove RV64E conflict Tsukasa OI
2023-07-25 13:27 ` Kito Cheng
2023-07-25 2:26 ` [PATCH 2/2] RISC-V: Add "lp64e" ABI support Tsukasa OI
2023-07-25 13:27 ` Kito Cheng
2023-08-31 3:21 ` [PATCH v2 0/3] RISC-V: Add ratified 'E' base ISA support with draft ABIs Tsukasa OI
2023-08-31 3:21 ` [PATCH v2 1/3] RISC-V: Remove RV64E conflict Tsukasa OI
2023-08-31 3:21 ` [PATCH v2 2/3] RISC-V: Add "lp64e" ABI support Tsukasa OI
2023-08-31 3:21 ` [PATCH v2 3/3] RISC-V: Add RV64E support to GDB Tsukasa OI
2023-09-05 9:08 ` [PATCH v3 0/3] RISC-V: Add ratified 'E' base ISA support with draft ABIs Tsukasa OI
2023-09-05 9:08 ` [PATCH v3 1/3] RISC-V: Remove RV64E conflict Tsukasa OI
2023-09-05 9:08 ` [PATCH v3 2/3] RISC-V: Add "lp64e" ABI support Tsukasa OI
2023-09-05 9:08 ` [PATCH v3 3/3] RISC-V: Add RV64E support to GDB Tsukasa OI
2023-09-25 3:07 ` [PATCH v3 0/3] RISC-V: Add ratified 'E' base ISA support with draft ABIs Nelson Chu
2023-09-25 8:04 ` Tsukasa OI [this message]
2023-10-16 8:20 ` 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=3515bb91-d607-420b-bc6b-e8084783d7df@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).