From: David Carlton <carlton@math.stanford.edu>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Joel Brobecker <brobecker@gnat.com>,
gdb-patches@sources.redhat.com, Jim Blandy <jimb@redhat.com>
Subject: Re: [rfa] struct dictionary
Date: Tue, 10 Jun 2003 15:58:00 -0000 [thread overview]
Message-ID: <ro1u1ax6i27.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <16101.9895.845174.90842@localhost.redhat.com>
On Mon, 9 Jun 2003 20:30:31 -0400, Elena Zannoni <ezannoni@redhat.com> said:
> Joel Brobecker writes:
>> > > Does anybody have a setup for testing mdebug? Daniel?
>> >
>> > Not me. Joel might? Since OSF/Tru64 is about the only thing left
>> > using it that we care about...
>>
>> We have a Tru64 machine, but no C++ compiler... Is this still ok?
> yes, this is generic stuff. Even though maybe some c++ symbols would
> make any performance difference more pronounced. The important
> change is the removal of the sorting for the symbol lists.
No, it will be fine performance-wise: I replaced the sorted lists by
hash tables. I'm just worried about correctness for mdebugread.c: I
had to touch it in enough places that I might have screwed up
everything and GDB will die a horrible death somewhere.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-06-10 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ro1k7dbwprh.fsf@jackfruit.Stanford.EDU>
2003-05-01 3:37 ` Eli Zaretskii
2003-05-01 21:15 ` David Carlton
2003-05-20 3:58 ` David Carlton
2003-06-09 22:39 ` Elena Zannoni
2003-06-09 22:55 ` Daniel Jacobowitz
2003-06-10 0:05 ` Joel Brobecker
2003-06-10 0:24 ` Elena Zannoni
2003-06-10 15:58 ` David Carlton [this message]
2003-06-10 16:43 ` David Carlton
2003-06-10 18:37 ` Elena Zannoni
2003-06-10 18:47 ` David Carlton
2003-06-11 1:20 ` Richard Henderson
2003-06-11 23:33 ` David Carlton
2003-06-13 0:15 ` Joel Brobecker
2003-06-13 0:52 ` David Carlton
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=ro1u1ax6i27.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=brobecker@gnat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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