public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/31821] move index_addrmap from dwarf2_per_bfd to mapped_gdb_index
Date: Fri, 31 May 2024 14:26:42 +0000	[thread overview]
Message-ID: <bug-31821-4717-CNpg6mLL6z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31821-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31821

--- Comment #3 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

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

commit 2e3b7a38930730b98e41f1393f8479488debb823
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu May 30 10:39:17 2024 -0600

    Move dwarf2_per_bfd::index_addrmap to mapped_gdb_index

    dwarf2_per_bfd::index_addrmap is only used by the .gdb_index reader,
    so this field can be moved to mapped_gdb_index instead.  Then,
    cooked_index_functions::find_per_cu can be removed in favor of a
    method on the index object.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31821
    Approved-By: Simon Marchi <simon.marchi@efficios.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-05-31 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 15:34 [Bug symtab/31821] New: " tromey at sourceware dot org
2024-05-30 15:34 ` [Bug symtab/31821] " tromey at sourceware dot org
2024-05-30 16:08 ` tromey at sourceware dot org
2024-05-30 16:38 ` tromey at sourceware dot org
2024-05-31 14:26 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-31 14:31 ` tromey at sourceware dot org

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=bug-31821-4717-CNpg6mLL6z@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).