From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH 0/6] Some buildsym cleanups
Date: Fri, 17 Apr 2026 12:24:02 -0600 [thread overview]
Message-ID: <20260417-list-in-scope-v1-0-0deb050fc03d@adacore.com> (raw)
This patch series cleans up buildsym a bit, in particular the context
pushing and popping code.
Regression tested on x86-64 Fedora 43.
Signed-off-by: Tom Tromey <tromey@adacore.com>
---
Tom Tromey (6):
Use scoped_restore for dwarf2_cu::list_in_scope
Remove some dead code from buildsym.c
Remove context_stack::depth
Change pop_context to return a block
Return void from buildsym_compunit::push_context
Rename context_stack and make it private
gdb/buildsym.c | 58 +++++++++++++------------------
gdb/buildsym.h | 100 ++++++++++++++++++++++++++++++------------------------
gdb/dwarf2/cu.h | 7 +---
gdb/dwarf2/read.c | 82 +++++++++++++++-----------------------------
4 files changed, 108 insertions(+), 139 deletions(-)
---
base-commit: bfd118583ed69db365265915d1a48eb719e997f5
change-id: 20260417-list-in-scope-4242b4cf355b
Best regards,
--
Tom Tromey <tromey@adacore.com>
next reply other threads:[~2026-04-17 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 18:24 Tom Tromey [this message]
2026-04-17 18:24 ` [PATCH 1/6] Use scoped_restore for dwarf2_cu::list_in_scope Tom Tromey
2026-04-17 18:24 ` [PATCH 2/6] Remove some dead code from buildsym.c Tom Tromey
2026-04-17 20:10 ` Simon Marchi
2026-04-17 18:24 ` [PATCH 3/6] Remove context_stack::depth Tom Tromey
2026-04-17 18:24 ` [PATCH 4/6] Change pop_context to return a block Tom Tromey
2026-04-17 20:11 ` Simon Marchi
2026-04-17 18:24 ` [PATCH 5/6] Return void from buildsym_compunit::push_context Tom Tromey
2026-04-17 20:22 ` Simon Marchi
2026-04-17 18:24 ` [PATCH 6/6] Rename context_stack and make it private Tom Tromey
2026-04-17 20:24 ` [PATCH 0/6] Some buildsym cleanups 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=20260417-list-in-scope-v1-0-0deb050fc03d@adacore.com \
--to=tromey@adacore.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