From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/6] Make remote-fileio per-target
Date: Sun, 31 Dec 2023 13:25:37 -0700 [thread overview]
Message-ID: <20231231-remote-fileio-v1-0-249cc6c440d9@tromey.com> (raw)
I noticed that the remote-fileio code uses a global. It seemed to me
that this should be per-target instead.
After writing this I noticed that gdbserver does not seem to implement
any of these packets. So, I don't think this can really be tested.
---
Tom Tromey (6):
Make remote_fio_func_map 'const'
Use vector in remote-fileio.c
Use methods for remote fileio
Remove sentinel from remote_fio_func_map
Move remote_fileio_data to header file
Store remote fileio state in remote_state
gdb/remote-fileio.c | 248 ++++++++++++++++++++++++----------------------------
gdb/remote-fileio.h | 42 +++++++--
gdb/remote.c | 8 +-
3 files changed, 153 insertions(+), 145 deletions(-)
---
base-commit: 276e7f5c8835cd300ee75d00556ab8839a30b9ef
change-id: 20231231-remote-fileio-24fbff0ba416
Best regards,
--
Tom Tromey <tom@tromey.com>
next 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 Tom Tromey [this message]
2023-12-31 20:25 ` [PATCH 1/6] Make remote_fio_func_map 'const' Tom Tromey
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-0-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).