From: Tom Tromey <tom@tromey.com>
To: Jan Vrany <jan.vrany@labware.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH v2 2/7] gdb: update expanded_symbols_functions::find_pc_sect_compunit_symtab
Date: Wed, 04 Mar 2026 14:19:38 -0700 [thread overview]
Message-ID: <87tsuvmgwl.fsf@tromey.com> (raw)
In-Reply-To: <20260304165914.3209106-3-jan.vrany@labware.com> (Jan Vrany's message of "Wed, 4 Mar 2026 16:59:09 +0000")
>>>>> "Jan" == Jan Vrany <jan.vrany@labware.com> writes:
Jan> This commit updates expanded_symbols_functions::find_pc_sect_compunit_symtab
Jan> to search all compunits rather than just returning null.
Jan> The original implementation (just return null) was based on reasoning
Jan> that its would suffice since find_compunit_symtab_for_pc_sect walks
Jan> all CUs anyway [1]. This commit is a preparation to simplify
Jan> find_compunit_symtab_for_pc_sect by removing that code.
Jan> Approved-By: Tom Tromey <tom@tromey.com>
Jan> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33829
Jan> + for (compunit_symtab &symtab : objfile->compunits ())
This "conflicts" with Simon's change to
expanded_symbols_functions -- whichever patch lands second will have to
be updated to account for the patch that lands first.
I just wanted to make sure you both are aware.
I think the change should be just looping over the local compunits, and
as far as I'm concerned that qualifies as obvious.
thanks,
Tom
next prev parent reply other threads:[~2026-03-04 21:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 16:59 [PATCH v2 0/7] Remove addrmap from blockvector Jan Vrany
2026-03-04 16:59 ` [PATCH v2 1/7] gdb: implement readnow_functions::find_pc_sect_compunit_symtab Jan Vrany
2026-03-04 16:59 ` [PATCH v2 2/7] gdb: update expanded_symbols_functions::find_pc_sect_compunit_symtab Jan Vrany
2026-03-04 21:19 ` Tom Tromey [this message]
2026-03-04 16:59 ` [PATCH v2 3/7] gdb: simplify find_compunit_symtab_for_pc_sect Jan Vrany
2026-03-04 16:59 ` [PATCH v2 4/7] gdb: update blockvector::lookup to handle non-contiguous blocks Jan Vrany
2026-03-04 16:59 ` [PATCH v2 5/7] gdb: do not set blockvector address map Jan Vrany
2026-03-04 16:59 ` [PATCH v2 6/7] gdb: remove address map from struct blockvector Jan Vrany
2026-03-04 16:59 ` [PATCH v2 7/7] gdb: add unit test for blockvector::lookup of non-contiguous blocks Jan Vrany
2026-03-10 18:14 ` [PING] Re: [PATCH v2 0/7] Remove addrmap from blockvector Jan Vraný
2026-04-22 10:29 ` [PATCH v3 " Jan Vrany
2026-04-28 18:55 ` [PING] " Jan Vrany
2026-05-08 9:14 ` Jan Vrany
2026-04-22 10:29 ` [PATCH v3 1/7] gdb: implement readnow_functions::find_pc_sect_compunit_symtab Jan Vrany
2026-04-22 10:29 ` [PATCH v3 2/7] gdb: update expanded_symbols_functions::find_pc_sect_compunit_symtab Jan Vrany
2026-04-22 10:29 ` [PATCH v3 3/7] gdb: simplify find_compunit_symtab_for_pc_sect Jan Vrany
2026-04-22 10:30 ` [PATCH v3 4/7] gdb: update blockvector::lookup to handle non-contiguous blocks Jan Vrany
2026-04-22 10:30 ` [PATCH v3 5/7] gdb: do not set blockvector address map Jan Vrany
2026-04-22 10:30 ` [PATCH v3 6/7] gdb: remove address map from struct blockvector Jan Vrany
2026-04-22 10:30 ` [PATCH v3 7/7] gdb: add unit test for blockvector::lookup of non-contiguous blocks Jan Vrany
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=87tsuvmgwl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.vrany@labware.com \
--cc=simon.marchi@polymtl.ca \
/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