From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] delete BLOCK_SHOULD_SORT
Date: Wed, 18 Sep 2002 19:25:00 -0000 [thread overview]
Message-ID: <20020919022513.GA31571@nevyn.them.org> (raw)
In-Reply-To: <ro1u1knrlkj.fsf@jackfruit.Stanford.EDU>
On Wed, Sep 18, 2002 at 03:15:40PM -0700, David Carlton wrote:
> I'd like to delete all occurences of BLOCK_SHOULD_SORT from GDB; it's
> really no longer necessary, and will get in the way of my dictionary
> work.
>
> The history, as I understand it, is that formerly symbols in blocks
> were always stored linearly; but, for blocks where the order didn't
> matter, the symbols were sorted to improve search time. Then blocks
> using hashtables were introduced; these are now used almost everywhere
> that sorted linear blocks had been previously used. In particular,
> blocks produced by buildsym.c, which is the vast majority of blocks,
> will never satisfy BLOCK_SHOULD_SORT.
...
> So, basically, making this change will get rid of some cruft, make an
> unnoticeable speed improvement to symbol manipulation stuff for normal
> usage, and when debugging ECOFF files, symbol table lookup will be a
> bit slower. (But it will still be correct: this is removing an
> optimization, but the unoptimized behavior will still work.) If
> anybody out there actually uses ECOFF and is bothered by this, clearly
> the best thing would be for that person to convert mdebugread.c to use
> the mechanisms in buildsym.c just like every other debugging format
> reader.
>
> I think the changes are pretty straightforward, though I'd appreciate
> it if somebody more conversant with ada-lang.c than I am could make
> sure I'm not missing anything with my change there.
For what it's worth, it all looks good (and worth doing!) to me.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-09-19 2:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 15:16 David Carlton
2002-09-18 19:25 ` Daniel Jacobowitz [this message]
2002-09-19 1:04 ` Paul N. Hilfinger
2002-09-19 6:29 ` Daniel Jacobowitz
2002-09-19 8:04 ` Andrew Cagney
2002-09-19 9:29 ` David Carlton
2002-09-22 16:02 ` Jim Blandy
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=20020919022513.GA31571@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@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