public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Alexander Smundak" <asmundak@cisco.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: "Cynbe ru Taren" <cynbe@muq.org>, <gdb@sources.redhat.com>
Subject: Re: parallelized 'ld'?
Date: Mon, 18 Aug 2003 19:02:00 -0000	[thread overview]
Message-ID: <02ff01c365bb$3612d740$5f3b45ab@amer.cisco.com> (raw)
In-Reply-To: <3F40EB8C.3040908@redhat.com>

Andrew,

> >> I believe one identified problem is how the symbol table uses hash
> >> tables.  The symbol tables are being given a careful upgrade.  Was this
> >> what you noticed?
> >
> > No, it is handling BINCL records in STABS. I have replaced the linear
search
> > in dbxread.c, function find_corresponding_bincl_psymtab() with hash
table,
> > and this shaved 3 minutes off the GDB initialization time in our case
> > (on 333MHz Sparc Ultra).
> > Please note that our compiler is gcc 2.95, and that this is for STABS
> > debugging
> > format. I can send the diffs to the interested parties; they are for 5.0
> > GDB, though.
>
> Ah.  Unless you/cisco have an assignment, a bug report pointing at the
> offending code would be better.
It turns out there is already an open PR#975:

Reporter's email:klee@apple.com
Number:975
Category:symtab
Synopsis:[RFA] Use hash to speed up BINCL/INCL processing.
Severity:serious
Priority:medium
State:open
Arrival-Date:Thu Jan 30 04:48:00 UTC 2003
Last-Modified:Sun Feb 16 04:18:00 UTC 2003

Alexander Smundak


      reply	other threads:[~2003-08-18 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200307150234.h6F2YsNW028337@tully.CS.Berkeley.EDU>
     [not found] ` <87d6f63jes.fsf@muq.org>
2003-08-16 14:46   ` Andrew Cagney
2003-08-18  0:40     ` Alexander Smundak
2003-08-18 15:06       ` Andrew Cagney
2003-08-18 19:02         ` Alexander Smundak [this message]

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='02ff01c365bb$3612d740$5f3b45ab@amer.cisco.com' \
    --to=asmundak@cisco.com \
    --cc=ac131313@redhat.com \
    --cc=cynbe@muq.org \
    --cc=gdb@sources.redhat.com \
    /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).