Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Kevin Buettner <kevinb@redhat.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb/dwarf2: Add symbols for function declarations
Date: Tue, 09 Sep 2025 18:40:31 -0600	[thread overview]
Message-ID: <871pofgmww.fsf@tromey.com> (raw)
In-Reply-To: <875xdwsye2.fsf@tromey.com> (Tom Tromey's message of "Fri, 05 Sep 2025 09:38:13 -0600")

I've been thinking about this some more.

Tom> Do these declaration symbols end up in .debug_names and .gdb_index?  I
Tom> suspect they should not.  (Particularly for .debug_names which
Tom> specifically excludes them in the text of the standard.)

This problem is a quandary, since if the symbols aren't added then there
will be behavior differences between the index and no-index cases.  OTOH
adding the symbols means going against the DWARF standard (we could
document it I guess?) and also would mean maybe bumping the .gdb_index
version and/or updating gold (if anyone still cares).

I did think of a possible upside, which is that maybe this would let us
get rid of the DIE range map in the indexer, since I guess scanning
nameless subroutine entries would no longer matter.

Tom

  parent reply	other threads:[~2025-09-10  0:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 19:45 Kevin Buettner
2025-08-12  0:23 ` Kevin Buettner
2025-08-12 14:48 ` Simon Marchi
2025-08-29 18:30 ` Andrew Burgess
2025-09-05 15:24 ` Andrew Burgess
2025-09-05 15:38 ` Tom Tromey
2025-09-05 16:20   ` Simon Marchi
2025-09-10  0:40   ` Tom Tromey [this message]
2025-09-13  0:55   ` Kevin Buettner

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=871pofgmww.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    /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