From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>,
Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH v2 0/5] gdb: Add basic support for LoongArch
Date: Fri, 11 Feb 2022 08:40:54 -0500 [thread overview]
Message-ID: <19233af1-49ce-15c6-3a34-dc4e2048f9a7@polymtl.ca> (raw)
In-Reply-To: <20220120005011.4531-1-yangtiezhu@loongson.cn>
On 2022-01-19 19:50, Tiezhu Yang wrote:
> In November 2021, my workmate Zhensong Liu submitted a single gdb
> patch [1] to support LoongArch which is a new RISC architecture,
> thanks Zhensong for his great work.
>
> It seems that the patch is too big to review, a patch series would be
> easier to review after internal discussion.
>
> This patchset only adds the minimal changes as simple as possible, the
> basic command "run", "break", "continue", "next", "step" and "quit" can
> be used to debug.
>
> This is the first step, we will submit other more patches step by step
> in the future, these small patches make an easily understood change that
> can be verified by reviewers, any comments will be much appreciated.
There should probably be a new entry for LoongArch in gdb/MAINTAINERS.
Simon
next prev parent reply other threads:[~2022-02-11 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 0:50 Tiezhu Yang
2022-01-20 0:50 ` [PATCH v2 1/5] gdb: LoongArch: Add initial target description support Tiezhu Yang
2022-01-20 0:50 ` [PATCH v2 2/5] gdb: LoongArch: Add initial baremetal support Tiezhu Yang
2022-01-20 0:50 ` [PATCH v2 3/5] gdb: LoongArch: Add initial Linux target support Tiezhu Yang
2022-01-20 0:50 ` [PATCH v2 4/5] gdb: LoongArch: Add initial native Linux support Tiezhu Yang
2022-01-20 0:50 ` [PATCH v2 5/5] gdb: LoongArch: Add Makefile, configure and NEWS Tiezhu Yang
2022-02-08 4:45 ` [PING] [PATCH v2 0/5] gdb: Add basic support for LoongArch Tiezhu Yang
2022-02-10 19:57 ` Tom Tromey
2022-02-11 12:50 ` Tiezhu Yang
2022-02-11 13:40 ` Simon Marchi [this message]
2022-02-12 7:59 ` Tiezhu Yang
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=19233af1-49ce-15c6-3a34-dc4e2048f9a7@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
--cc=yangtiezhu@loongson.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).