From: simon.marchi@polymtl.ca
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH 0/5] Some semi-random DWARF cleanups
Date: Sat, 17 Jan 2026 01:02:30 -0500 [thread overview]
Message-ID: <20260117060335.691691-1-simon.marchi@polymtl.ca> (raw)
From: Simon Marchi <simon.marchi@polymtl.ca>
I am working on a patch to handle foreign TUs when generating the
.debug_names index. These are the cleanups I accumulated, that I think
make sense on their own.
Simon Marchi (5):
gdb/dwarf: merge one CU/TU code path
gdb/dwarf: move DWP htab nullptr check to lookup_dwo_unit_in_dwp
gdb/dwarf: add comments to debug_names::build
gdb/dwarf: rename some abbrev-related things in debug_names writer
gdb/dwarf: add unit_lists structure to index writer
gdb/dwarf2/index-write.c | 78 ++++++++++++++++++++++++++--------------
gdb/dwarf2/read.c | 63 +++++++++++++-------------------
2 files changed, 76 insertions(+), 65 deletions(-)
base-commit: ec2ec78ce03f02e1c8bf2ab30625a934ae52682f
--
2.52.0
next reply other threads:[~2026-01-17 6:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 6:02 simon.marchi [this message]
2026-01-17 6:02 ` [PATCH 1/5] gdb/dwarf: merge one CU/TU code path simon.marchi
2026-01-17 6:02 ` [PATCH 2/5] gdb/dwarf: move DWP htab nullptr check to lookup_dwo_unit_in_dwp simon.marchi
2026-01-17 6:02 ` [PATCH 3/5] gdb/dwarf: add comments to debug_names::build simon.marchi
2026-01-17 6:02 ` [PATCH 4/5] gdb/dwarf: rename some abbrev-related things in debug_names writer simon.marchi
2026-01-17 6:02 ` [PATCH 5/5] gdb/dwarf: add unit_lists structure to index writer simon.marchi
2026-01-20 17:00 ` Tom Tromey
2026-01-20 17:33 ` Simon Marchi
2026-01-20 20:42 ` Tom Tromey
2026-01-20 21:12 ` Simon Marchi
2026-01-20 17:00 ` [PATCH 0/5] Some semi-random DWARF cleanups Tom Tromey
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=20260117060335.691691-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