From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 9/9] add short-circuit logic to elfread.c
Date: Mon, 21 Oct 2013 18:50:00 -0000 [thread overview]
Message-ID: <877gd6jw68.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CADPb22SXNWAsZVv1neiTjGEkiL1QBVV7D=y9QPsosfyyk_k+-A@mail.gmail.com> (Doug Evans's message of "Mon, 21 Oct 2013 09:44:43 -0700")
>> Nope. I can add it back somehow if you need it. Though at the same
>> time I would like to know what you use it for. I never figured out how
>> the current statistic could be useful.
Doug> I don't "need" it, it's just good data and was curious.
The distinction I was trying to draw wasn't whether it was needed or not
needed, but whether it was useful and if so, what for. I read your
response here as saying it is useful. But could you explain what for?
What use is there for it?
I understand wanting to know the size of the table that is actually
constructed. This is good for seeing where all the memory goes. But I
never thought of a use for "number of minimal symbols we discarded".
Tom
next prev parent reply other threads:[~2013-10-21 18:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 17:50 [PATCH v2 0/9] share minimal symbols across objfiles Tom Tromey
2013-10-17 17:50 ` [PATCH v2 3/9] make MSYMBOL_VALUE_ADDRESS an rvalue Tom Tromey
2013-10-17 17:50 ` [PATCH v2 7/9] move minimal symbols to per-bfd Tom Tromey
2013-10-17 17:50 ` [PATCH v2 8/9] split out elf_read_minimal_symbols Tom Tromey
2013-10-17 17:50 ` [PATCH v2 5/9] start change to progspace independence Tom Tromey
2013-10-17 17:50 ` [PATCH v2 4/9] use bound_minsym as result for lookup_minimal_symbol et al Tom Tromey
2013-10-17 17:50 ` [PATCH v2 2/9] change minsym representation Tom Tromey
2013-10-17 17:50 ` [PATCH v2 9/9] add short-circuit logic to elfread.c Tom Tromey
2013-10-18 22:46 ` Doug Evans
2013-10-20 19:53 ` Tom Tromey
2013-10-21 16:44 ` Doug Evans
2013-10-21 18:50 ` Tom Tromey [this message]
2013-10-21 19:52 ` Doug Evans
2013-10-29 18:31 ` Tom Tromey
2013-10-17 17:50 ` [PATCH v2 1/9] introduce minimal_symbol_upper_bound Tom Tromey
2013-10-18 22:01 ` Doug Evans
2013-10-21 16:23 ` Tom Tromey
2013-10-21 16:47 ` Doug Evans
2013-10-17 18:34 ` [PATCH v2 6/9] change minsyms not to be relocated at read-time Tom Tromey
2013-10-18 10:32 ` [PATCH v2 0/9] share minimal symbols across objfiles Will Newton
2013-10-18 18:35 ` Tom Tromey
2014-01-13 20:59 ` Tom Tromey
2014-02-26 18:48 ` Pedro Alves
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=877gd6jw68.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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).