public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/16998] perf improvements for searching GLOBAL_BLOCK
Date: Sat, 11 Feb 2023 17:04:46 +0000 [thread overview]
Message-ID: <bug-16998-4717-4FuyzShWkw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16998-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16998
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
> But .gdb_index knows exactly which symtab(s) to look in.
...
> So why not just always use .gdb_index for GLOBAL_BLOCK lookups?
It makes sense to me.
Basically we'd want to extend the "quick" functionality
to some symtab-level operations as well, or maybe just
change the lookup code and ensure that the quick methods
also know to iterate over already-expanded symtabs.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-11 17:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 19:49 [Bug symtab/16998] New: " dje at google dot com
2014-05-29 20:37 ` [Bug symtab/16998] " dje at google dot com
2014-05-30 2:26 ` dje at google dot com
2023-02-11 17:04 ` tromey at sourceware dot org [this message]
2023-09-18 8:06 ` tromey at sourceware dot org
2024-12-19 16:05 ` tromey at sourceware dot org
2024-12-19 16:12 ` tromey at sourceware dot org
2025-01-02 20:36 ` tromey at sourceware dot org
2025-01-02 20:38 ` tromey at sourceware dot org
2025-01-03 12:38 ` sam at gentoo dot org
2025-01-03 13:48 ` sam at gentoo dot org
2025-01-05 18:28 ` tromey at sourceware dot org
2025-01-05 18:43 ` tromey at sourceware dot org
2025-01-05 19:25 ` tromey at sourceware dot org
2025-01-08 0:30 ` tromey at sourceware dot org
2025-01-20 16:46 ` tromey at sourceware dot org
2025-01-24 21:08 ` tromey at sourceware dot org
2025-02-22 0:45 ` tromey at sourceware dot org
2025-03-06 14:49 ` tromey at sourceware dot org
2025-03-12 9:59 ` sam at gentoo dot org
2025-03-12 10:00 ` sam at gentoo dot org
2025-05-03 23:13 ` tromey at sourceware dot org
2025-05-23 14:53 ` tromey at sourceware dot org
2025-09-10 22:18 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:18 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:18 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:18 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:18 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:18 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:18 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:18 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:19 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:19 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:19 ` cvs-commit at gcc dot gnu.org
2025-09-10 22:19 ` cvs-commit at gcc dot gnu.org
2025-09-10 23:58 ` tromey at sourceware dot org
2025-09-11 0:02 ` tromey at sourceware dot org
2025-09-11 0:08 ` tromey at sourceware dot org
2025-09-21 18:05 ` tromey at sourceware dot org
2025-10-20 16:30 ` sam at gentoo dot org
2025-10-20 16:31 ` sam at gentoo 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-16998-4717-4FuyzShWkw@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).