From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@palves.net>, John Baldwin <jhb@freebsd.org>,
Kevin Buettner <kevinb@redhat.com>,
Andrew Burgess <aburgess@redhat.com>,
Luis Machado <luis.machado@arm.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
Tom Tromey <tom@tromey.com>, Tom de Vries <tdevries@suse.de>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re:[PING] [PATCH v1 0/7] gdb: Modify some code about syscalls XML
Date: Mon, 18 Mar 2024 17:27:45 +0800 [thread overview]
Message-ID: <abf4efc0-416d-de09-f21c-46b024aa593e@loongson.cn> (raw)
In-Reply-To: <20240229083910.9991-1-yangtiezhu@loongson.cn>
On 02/29/2024 04:39 PM, Tiezhu Yang wrote:
> Tiezhu Yang (7):
> gdb: syscalls: Update linux-defaults.xml.in
> gdb: syscalls: Update .xml.in files for some archs
> gdb: syscalls: Update .xml files for some archs
> gdb: syscalls: Add loongarch-linux.xml.in
> gdb: syscalls: Generate loongarch-linux.xml
> gdb: syscalls: Add loongarch case in update-linux-from-src.sh
> gdb: LoongArch: Set the correct XML syscall filename
>
> gdb/data-directory/Makefile.in | 1 +
> gdb/loongarch-linux-tdep.c | 7 +
> gdb/syscalls/amd64-linux.xml | 11 +
> gdb/syscalls/amd64-linux.xml.in | 11 +
> gdb/syscalls/i386-linux.xml | 11 +
> gdb/syscalls/i386-linux.xml.in | 11 +
> gdb/syscalls/linux-defaults.xml.in | 3 +
> gdb/syscalls/loongarch-linux.xml | 327 +++++++++++++++++++++++++
> gdb/syscalls/loongarch-linux.xml.in | 331 ++++++++++++++++++++++++++
> gdb/syscalls/mips-n32-linux.xml | 11 +
> gdb/syscalls/mips-n32-linux.xml.in | 11 +
> gdb/syscalls/mips-n64-linux.xml | 11 +
> gdb/syscalls/mips-n64-linux.xml.in | 11 +
> gdb/syscalls/mips-o32-linux.xml | 11 +
> gdb/syscalls/mips-o32-linux.xml.in | 11 +
> gdb/syscalls/ppc-linux.xml | 11 +
> gdb/syscalls/ppc-linux.xml.in | 11 +
> gdb/syscalls/ppc64-linux.xml | 11 +
> gdb/syscalls/ppc64-linux.xml.in | 11 +
> gdb/syscalls/s390-linux.xml | 12 +
> gdb/syscalls/s390-linux.xml.in | 12 +
> gdb/syscalls/s390x-linux.xml | 12 +
> gdb/syscalls/s390x-linux.xml.in | 12 +
> gdb/syscalls/sparc-linux.xml | 11 +
> gdb/syscalls/sparc-linux.xml.in | 11 +
> gdb/syscalls/sparc64-linux.xml | 11 +
> gdb/syscalls/sparc64-linux.xml.in | 11 +
> gdb/syscalls/update-linux-from-src.sh | 4 +
> 28 files changed, 919 insertions(+)
> create mode 100644 gdb/syscalls/loongarch-linux.xml
> create mode 100644 gdb/syscalls/loongarch-linux.xml.in
Hi all,
The changes are almost generated through scripts, however I think it
is necessary to make sure that the patches have been approved by the
Global Maintainers before pushing them, I am looking forward to your
reply.
Thanks,
Tiezhu
next prev parent reply other threads:[~2024-03-18 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 8:39 Tiezhu Yang
2024-02-29 8:39 ` [PATCH v1 1/7] gdb: syscalls: Update linux-defaults.xml.in Tiezhu Yang
2024-02-29 8:39 ` [PATCH v1 2/7] gdb: syscalls: Update .xml.in files for some archs Tiezhu Yang
2024-02-29 8:39 ` [PATCH v1 3/7] gdb: syscalls: Update .xml " Tiezhu Yang
2024-02-29 8:39 ` [PATCH v1 4/7] gdb: syscalls: Add loongarch-linux.xml.in Tiezhu Yang
2024-03-20 20:51 ` Pedro Alves
2024-03-21 2:02 ` Tiezhu Yang
2024-02-29 8:39 ` [PATCH v1 5/7] gdb: syscalls: Generate loongarch-linux.xml Tiezhu Yang
2024-02-29 8:39 ` [PATCH v1 6/7] gdb: syscalls: Add loongarch case in update-linux-from-src.sh Tiezhu Yang
2024-02-29 8:39 ` [PATCH v1 7/7] gdb: LoongArch: Set the correct XML syscall filename Tiezhu Yang
2024-03-13 1:18 ` [PING] [PATCH v1 0/7] gdb: Modify some code about syscalls XML Tiezhu Yang
2024-03-18 9:27 ` Tiezhu Yang [this message]
2024-03-19 16:29 ` John Baldwin
2024-03-20 10:53 ` 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=abf4efc0-416d-de09-f21c-46b024aa593e@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=kevinb@redhat.com \
--cc=luis.machado@arm.com \
--cc=pedro@palves.net \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
--cc=tom@tromey.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).