From: Andrew Cagney <ac131313@redhat.com>
To: Cynbe ru Taren <cynbe@muq.org>
Cc: Paul Hilfinger <hilfingr@EECS.Berkeley.EDU>,
gdb@sources.redhat.com, Alexander Smundak <asmundak@cisco.com>
Subject: Re: parallelized 'ld'?
Date: Sat, 16 Aug 2003 14:46:00 -0000 [thread overview]
Message-ID: <3F3E43A5.1000906@redhat.com> (raw)
In-Reply-To: <87d6f63jes.fsf@muq.org>
[switching mailing lists from binutils@ to gdb@]
> * "gdb used to take inordinate amount of time to load on our platform. The
> fix was trivial, which likely means that few people ever use GDB on
> such large executables."
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?
As for using GDB on large programs, mozilla is (or was) the reference -
its startup has gone from impossible to tolerable. I believe users now
also have their sights on eclipse (compiled with gcj). So increasing
demand is definitly there.
Andrew
next parent reply other threads:[~2003-08-16 14:46 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 [this message]
2003-08-18 0:40 ` Alexander Smundak
2003-08-18 15:06 ` Andrew Cagney
2003-08-18 19:02 ` Alexander Smundak
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=3F3E43A5.1000906@redhat.com \
--to=ac131313@redhat.com \
--cc=asmundak@cisco.com \
--cc=cynbe@muq.org \
--cc=gdb@sources.redhat.com \
--cc=hilfingr@EECS.Berkeley.EDU \
/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).