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] Remove unused field cooked_index::m_start
Date: Fri, 13 May 2022 19:53:14 +0000 (GMT)	[thread overview]
Message-ID: <20220513195314.E14C73982428@sourceware.org> (raw)

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

commit 5400535a70cd5f7626f4110a69508ad9ff669328
Author: Tom Tromey <tromey@adacore.com>
Date:   Fri May 13 13:47:39 2022 -0600

    Remove unused field cooked_index::m_start
    
    cooked_index::m_start is unused and can be removed.  I think this was
    a leftover from a previous approach in the index finalization code,
    and then when rewriting it I forgot to remove it.
    
    Tested by rebuilding.

Diff:
---
 gdb/dwarf2/cooked-index.h | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/gdb/dwarf2/cooked-index.h b/gdb/dwarf2/cooked-index.h
index 1d229586948..ad4de05ba52 100644
--- a/gdb/dwarf2/cooked-index.h
+++ b/gdb/dwarf2/cooked-index.h
@@ -230,11 +230,6 @@ private:
   /* If we found "main" or an entry with 'is_main' set, store it
      here.  */
   cooked_index_entry *m_main = nullptr;
-  /* When constructing the index, entries are stored on a linked list.
-     This member points to the head of that list.  Later, they are
-     entered into the hash table, at which point this is no longer
-     used.  */
-  cooked_index_entry *m_start = nullptr;
   /* The addrmap.  This maps address ranges to dwarf2_per_cu_data
      objects.  */
   addrmap *m_addrmap = nullptr;


                 reply	other threads:[~2022-05-13 19:53 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=20220513195314.E14C73982428@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).