From: Eli Zaretskii <eliz@gnu.org>
To: Timur <timurgol007@gmail.com>
Cc: gdb-patches@sourceware.org, guinevere@redhat.com
Subject: Re: [PING][PATCH v8] This commit adds record full support for rv64gc instruction set
Date: Mon, 10 Feb 2025 21:30:02 +0200 [thread overview]
Message-ID: <86jz9xy4w5.fsf@gnu.org> (raw)
In-Reply-To: <20250210180703.584644-1-timurgol007@gmail.com> (message from Timur on Mon, 10 Feb 2025 21:07:03 +0300)
> From: Timur <timurgol007@gmail.com>
> Cc: Timur <timurgol007@gmail.com>,
> Guinevere Larsen <guinevere@redhat.com>
> Date: Mon, 10 Feb 2025 21:07:03 +0300
>
> gdb/NEWS | 2 +
> gdb/configure.tgt | 5 +-
> gdb/doc/gdb.texinfo | 2 +-
> gdb/riscv-canonicalize-syscall-gen.c | 342 +++++++++
> gdb/riscv-linux-tdep.c | 260 +++++++
> gdb/riscv-linux-tdep.h | 29 +
> gdb/riscv-tdep.c | 710 +++++++++++++++++-
> gdb/riscv-tdep.h | 14 +
> .../riscv-canonicalize-syscall-gen.py | 148 ++++
> gdb/testsuite/lib/gdb.exp | 3 +-
> 10 files changed, 1506 insertions(+), 9 deletions(-)
> create mode 100644 gdb/riscv-canonicalize-syscall-gen.c
> create mode 100644 gdb/riscv-linux-tdep.h
> create mode 100755 gdb/syscalls/riscv-canonicalize-syscall-gen.py
Thanks, the changes for the documentation are okay.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2025-02-10 19:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 22:26 [PATCH] gdb/riscv: Add record support for rv64gc instructions Timur
2024-11-18 19:46 ` Guinevere Larsen
2024-11-26 14:17 ` [PATCH v2] " Timur
2024-11-27 14:23 ` Guinevere Larsen
2024-12-03 18:30 ` [PATCH v3] " Timur
2024-12-13 18:10 ` Guinevere Larsen
2024-12-17 0:10 ` [PATCH v4] This commit adds record full support for rv64gc instruction set Timur
2024-12-17 14:23 ` Guinevere Larsen
2024-12-23 15:12 ` [PATCH v5] " Timur
2024-12-23 18:55 ` Guinevere Larsen
2024-12-31 16:09 ` [PATCH v6] " Timur
2025-01-10 18:12 ` Guinevere Larsen
2025-01-16 15:48 ` [PATCH v7] " Timur
2025-02-10 18:07 ` [PING][PATCH v8] " Timur
2025-02-10 19:30 ` Eli Zaretskii [this message]
2025-02-11 22:06 ` [PATCH] " Timur
2025-02-26 11:14 ` [PATCH][PING] " Timur
2025-03-13 10:38 ` Andrew Burgess
2025-03-13 15:03 ` [PATCH] " Andrew Burgess
2025-03-18 18:49 ` [PATCH v8] " Timur
2025-03-31 17:50 ` [PING][PATCH] " Timur
2025-04-08 12:33 ` Timur Golubovich
2025-04-10 9:16 ` Andrew Burgess
2025-04-10 9:16 ` [PATCH v8] " Andrew Burgess
2025-04-10 11:55 ` Timur
2025-04-14 7:40 ` Andrew Burgess
2025-04-14 8:44 ` Timur Golubovich
2025-04-14 12:03 ` Guinevere Larsen
2025-04-22 17:36 ` Timur Golubovich
2025-04-23 12:13 ` Guinevere Larsen
2025-04-23 14:01 ` Aktemur, Tankut Baris
2025-04-23 14:13 ` Guinevere Larsen
2025-04-23 14:39 ` Timur Golubovich
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=86jz9xy4w5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--cc=timurgol007@gmail.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