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/8367] [RFA]  performance improvement of lookup_partial_symtab
Date: Fri, 06 Jan 2023 19:42:17 +0000	[thread overview]
Message-ID: <bug-8367-4717-r8KCbqdZVP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-8367-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
                 CC|                            |tromey at sourceware dot org
             Status|ASSIGNED                    |RESOLVED

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
Note to self, to compile you must use:

$ gnatmake -g main -aImany_files

With git master this is very quick:

(gdb) maint time 1
(gdb) list
/home/tromey/gdb/PRs/pr8367-basenames/many_files/pack_0001_test.ads:22023-01-06
12:40:09.325 - command started
1       package Pack_0001_Test is
2          pragma Pure;
3          Var_0001_Test : constant String := "0001";
4       end Pack_0001_Test;
2023-01-06 12:40:09.359 - command finished
Command execution time: 0.034019 (cpu), 0.034398 (wall)


So I think this is fixed.

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

  parent reply	other threads:[~2023-01-06 19:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-8367-4717@http.sourceware.org/bugzilla/>
2011-12-14 16:07 ` cvs-commit at gcc dot gnu.org
2011-12-14 16:09 ` cvs-commit at gcc dot gnu.org
2015-06-16 17:28 ` dje at google dot com
2023-01-06 19:42 ` tromey at sourceware dot org [this message]
     [not found] <20030626173801.8367.guitton@act-europe.fr>
2009-01-05 19:39 ` tromey at redhat dot com

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-8367-4717-r8KCbqdZVP@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).