From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Handle dereferencing Rust trait objects
Date: Fri, 17 Nov 2017 17:30:00 -0000 [thread overview]
Message-ID: <87375c95jg.fsf@tromey.com> (raw)
In-Reply-To: <87bmk19554.fsf@tromey.com> (Tom Tromey's message of "Thu, 16 Nov 2017 16:26:47 -0700")
Tom> I could do something else. A vector of pairs, sorted by address; or an
Tom> htab_t.
Pedro> Can you say something about the number of elements that usually
Pedro> ends up in this map in some reasonably sized Rust-using app (Firefox?)?
Tom> I will look at this tomorrow.
I had a bit of a panic when I ran this on libxul and got a count of
501908 symbols.
However, my first attempt counted incorrectly; there are actually only
46488 unique LOC_STATIC psymbols in libxul. This roughly conforms to
the idea that the psymbol cache is ~90% effective.
Anyway, we discussed it on irc a bit, and I think I'll switch to the
sorted vector of pairs. This will save some space, and isn't much
slower or harder to code.
Tom
prev parent reply other threads:[~2017-11-17 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 21:24 Tom Tromey
2017-11-15 21:28 ` Tom Tromey
2017-11-16 16:40 ` Pedro Alves
2017-11-16 23:13 ` Tom Tromey
2017-11-17 15:39 ` Pedro Alves
2017-11-16 16:35 ` Pedro Alves
2017-11-16 23:26 ` Tom Tromey
2017-11-17 17:30 ` Tom Tromey [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=87375c95jg.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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