From: Pedro Alves <pedro@palves.net>
To: Tiezhu Yang <yangtiezhu@loongson.cn>, gdb-patches@sourceware.org
Subject: Re: [PATCH v1 4/7] gdb: syscalls: Add loongarch-linux.xml.in
Date: Wed, 20 Mar 2024 20:51:35 +0000 [thread overview]
Message-ID: <75a1ad9b-5987-4b45-b52f-174bb359b70e@palves.net> (raw)
In-Reply-To: <20240229083910.9991-5-yangtiezhu@loongson.cn>
On 2024-02-29 08:39, Tiezhu Yang wrote:
>
> There exist some __NR3264_ prefixed syscall numbers, replace them
> with digital numbers according to /usr/include/asm-generic/unistd.h
> and sort them by syscall number manually, maybe we can modify the
> script to do it automatically in the future.
>
> <syscall name="fcntl" number="__NR3264_fcntl"/>
> <syscall name="statfs" number="__NR3264_statfs"/>
> <syscall name="fstatfs" number="__NR3264_fstatfs"/>
> <syscall name="truncate" number="__NR3264_truncate"/>
> <syscall name="ftruncate" number="__NR3264_ftruncate"/>
> <syscall name="lseek" number="__NR3264_lseek"/>
> <syscall name="sendfile" number="__NR3264_sendfile"/>
> <syscall name="mmap" number="__NR3264_mmap"/>
> <syscall name="fadvise64" number="__NR3264_fadvise64"/>
>
This should at least be mentioned here ...
...
> +<!-- This file was generated using the following file:
> +
> + <sys/syscall.h>
> +
> + The file mentioned above belongs to the Linux Kernel. -->
.... to help the next person who regenerates this file understand what needs to be done.
next prev parent reply other threads:[~2024-03-20 20:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 8:39 [PATCH v1 0/7] gdb: Modify some code about syscalls XML 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 [this message]
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
2024-03-19 16:29 ` [PING] " 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=75a1ad9b-5987-4b45-b52f-174bb359b70e@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--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).