From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Make lwp_info use intrusive_list
Date: Sat, 28 Aug 2021 10:58:42 -0400 [thread overview]
Message-ID: <20210828145845.1034686-1-simon.marchi@polymtl.ca> (raw)
The goal of this series is to replace the manually maintained linked
list of lwp_info objects with an intrusive_list. No user-visible
changes expected, no regressions seen on Linux / x86-64.
Simon Marchi (3):
gdb: make lwp_info non-POD
gdb: add destructor to lwp_info
gdb: use intrusive_list for linux-nat lwp_list
gdb/ia64-linux-nat.c | 8 ++---
gdb/linux-nat.c | 84 ++++++++++++++++++-------------------------
gdb/linux-nat.h | 73 ++++++++++++++++++++-----------------
gdb/linux-thread-db.c | 3 +-
gdb/mips-linux-nat.c | 7 ++--
5 files changed, 80 insertions(+), 95 deletions(-)
--
2.33.0
next reply other threads:[~2021-08-28 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 14:58 Simon Marchi [this message]
2021-08-28 14:58 ` [PATCH 1/3] gdb: make lwp_info non-POD Simon Marchi
2021-08-28 14:58 ` [PATCH 2/3] gdb: add destructor to lwp_info Simon Marchi
2021-08-28 14:58 ` [PATCH 3/3] gdb: use intrusive_list for linux-nat lwp_list Simon Marchi
2021-09-28 2:34 ` [PATCH 0/3] Make lwp_info use intrusive_list Simon Marchi
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=20210828145845.1034686-1-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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).