public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org,  Tom de Vries <tdevries@suse.de>
Subject: Re: [PATCH gdb/symtab v2 0/7] Compute DWARF entry parents across CUs
Date: Tue, 16 Apr 2024 11:54:14 -0600	[thread overview]
Message-ID: <875xwh19dl.fsf@tromey.com> (raw)
In-Reply-To: <20240408-die-map-madness-v2-0-6741626d544d@tromey.com> (Tom Tromey's message of "Mon, 08 Apr 2024 15:11:36 -0600")

>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:

Tom> This is a different approach to a patch series that Tom de Vries sent.
Tom> The bug here is that gdb won't always correctly compute the parent of
Tom> an entry in some cross-CU reference cases.

Tom> I've included a few of Tom's patches in this series.  The main
Tom> difference overall is that this one incorporates the parent
Tom> computation into the finalization loop, so the work is parallelized.

Tom> Regression tested on x86-64 Fedora 38 with the cc-with-dwz board.
Tom> There is still one bug (the inlining one), but I believe that one
Tom> requires a different fix.

I rebased this and re-regression tested it, and now I am checking it in.

Tom

      parent reply	other threads:[~2024-04-16 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 21:11 Tom Tromey
2024-04-08 21:11 ` [PATCH gdb/symtab v2 1/7] Refactor condition in scan_attributes Tom Tromey
2024-04-08 21:11 ` [PATCH v2 2/7] Change handling of DW_TAG_enumeration_type in DWARF scanner Tom Tromey
2024-04-08 21:11 ` [PATCH v2 3/7] Add move operators for addrmap Tom Tromey
2024-04-08 21:11 ` [PATCH v2 4/7] Introduce class parent_map for DIE range map Tom Tromey
2024-04-08 21:11 ` [PATCH v2 5/7] Correctly handle DIE parent computations Tom Tromey
2024-04-08 21:11 ` [PATCH gdb/testsuite v2 6/7] Add gdb.dwarf2/forward-spec-inter-cu.exp Tom Tromey
2024-04-08 21:11 ` [PATCH gdb/testsuite v2 7/7] Add gdb.dwarf2/backward-spec-inter-cu.exp Tom Tromey
2024-04-16 17:54 ` Tom Tromey [this message]

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=875xwh19dl.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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).