From: Hui Li <lihui@loongson.cn>
To: gdb-patches@sourceware.org
Cc: Hui Li <lihui@loongson.cn>
Subject: [PATCH 0/2] gdb: LoongArch: Modify the info reg command
Date: Thu, 16 Feb 2023 19:20:18 +0800 [thread overview]
Message-ID: <20230216112020.25610-1-lihui@loongson.cn> (raw)
Hui Li (2):
gdb: LoongArch: Modify the result of the info reg command
gdb: LoongArch: Support reg aliases in info reg command
gdb/loongarch-tdep.c | 60 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 60 insertions(+)
--
2.38.0
next reply other threads:[~2023-02-16 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 11:20 Hui Li [this message]
2023-02-16 11:20 ` [PATCH 1/2] gdb: LoongArch: Modify the result of " Hui Li
2023-02-16 11:20 ` [PATCH 2/2] gdb: LoongArch: Support reg aliases in " Hui Li
2023-02-23 12:38 ` [PATCH 0/2] gdb: LoongArch: Modify the " 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=20230216112020.25610-1-lihui@loongson.cn \
--to=lihui@loongson.cn \
--cc=gdb-patches@sourceware.org \
/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).