From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/6] Make remote_fio_func_map 'const'
Date: Sun, 31 Dec 2023 13:25:38 -0700 [thread overview]
Message-ID: <20231231-remote-fileio-v1-1-249cc6c440d9@tromey.com> (raw)
In-Reply-To: <20231231-remote-fileio-v1-0-249cc6c440d9@tromey.com>
This changes remote_fio_func_map to be const, letting it move into the
readonly data section.
---
gdb/remote-fileio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/remote-fileio.c b/gdb/remote-fileio.c
index 10bc86c1ba5..367edb54f74 100644
--- a/gdb/remote-fileio.c
+++ b/gdb/remote-fileio.c
@@ -1101,7 +1101,7 @@ remote_fileio_func_system (remote_target *remote, char *buf)
remote_fileio_return_success (remote, WEXITSTATUS (ret));
}
-static struct {
+static const struct {
const char *name;
void (*func)(remote_target *remote, char *);
} remote_fio_func_map[] = {
--
2.43.0
next prev parent reply other threads:[~2023-12-31 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 20:25 [PATCH 0/6] Make remote-fileio per-target Tom Tromey
2023-12-31 20:25 ` Tom Tromey [this message]
2023-12-31 20:25 ` [PATCH 2/6] Use vector in remote-fileio.c Tom Tromey
2024-01-01 14:20 ` Lancelot SIX
2024-01-01 18:39 ` Simon Marchi
2023-12-31 20:25 ` [PATCH 3/6] Use methods for remote fileio Tom Tromey
2023-12-31 20:25 ` [PATCH 4/6] Remove sentinel from remote_fio_func_map Tom Tromey
2023-12-31 20:25 ` [PATCH 5/6] Move remote_fileio_data to header file Tom Tromey
2023-12-31 20:25 ` [PATCH 6/6] Store remote fileio state in remote_state Tom Tromey
2024-01-01 14:28 ` [PATCH 0/6] Make remote-fileio per-target Lancelot SIX
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=20231231-remote-fileio-v1-1-249cc6c440d9@tromey.com \
--to=tom@tromey.com \
--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).