public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Don't add type linkage names to cooked index
Date: Mon, 17 Oct 2022 16:10:55 +0000 (GMT)	[thread overview]
Message-ID: <20221017161055.4B8D53858291@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=acd121de32c3924347f228d8f27000a09b9c8949

commit acd121de32c3924347f228d8f27000a09b9c8949
Author: Tom Tromey <tromey@adacore.com>
Date:   Fri Oct 14 07:08:57 2022 -0600

    Don't add type linkage names to cooked index
    
    The compiler will sometimes emit a linkage name for a type, like:
    
        <1d3>   DW_AT_linkage_name: (indirect string, offset: 0x106f): 11__mbstate_t
    
    These names aren't very useful, and this patch changes the DWARF
    reader so that they are ignored by the cooked index.

Diff:
---
 gdb/dwarf2/read.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
index e62f9752a80..33dfd52b362 100644
--- a/gdb/dwarf2/read.c
+++ b/gdb/dwarf2/read.c
@@ -17991,11 +17991,6 @@ tag_can_have_linkage_name (enum dwarf_tag tag)
 {
   switch (tag)
     {
-      /* We include types here because an anonymous C++ type might
-	 have a name for linkage purposes.  */
-    case DW_TAG_class_type:
-    case DW_TAG_structure_type:
-    case DW_TAG_union_type:
     case DW_TAG_variable:
     case DW_TAG_subprogram:
       return true;

                 reply	other threads:[~2022-10-17 16:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221017161055.4B8D53858291@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=gdb-cvs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).