From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, ratmice@gmail.com
Subject: Re: [RFA] massively speed up "info var foo" on large programs
Date: Mon, 04 Jun 2012 15:03:00 -0000 [thread overview]
Message-ID: <4FCCCE27.2060804@redhat.com> (raw)
In-Reply-To: <CADPb22Tp5auHhj+-=qHW9XDEJfh-N1HjSBGYYYKVXutT-S0Zpw@mail.gmail.com>
On 06/04/2012 05:06 AM, Doug Evans wrote:
> GDB's symbol support is a mess (IMO), and I wanted
> a name and usage to restrict it to the task at hand. Anything more
> general and I was pretty sure this patch would get bogged down.
That'd be a bit beyond what I requested. ;-)
> Later on I want to revamp the symbol API, but I don't want this patch
> tied down by that.
Certainly. That'd clearly need to be a separate change.
> (For example, I don't want to bubble up the semantics of
> demangle_for_lookup to the caller of this function. Here we have an
> msymbol, we know we have a mangled name. If you want, I can go with
> lookup_symbol_in_objfile but rename it to
> lookup_symbol_in_objfile_from_linkage_name or some such.)
That'd be fine with me. Thanks.
--
Pedro Alves
next prev parent reply other threads:[~2012-06-04 15:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 17:59 Doug Evans
2012-05-24 21:28 ` Doug Evans
2012-05-25 4:29 ` Matt Rice
2012-05-25 8:21 ` Doug Evans
2012-05-25 8:51 ` Pedro Alves
2012-05-28 4:49 ` Doug Evans
2012-05-31 18:53 ` Doug Evans
2012-06-01 19:38 ` Pedro Alves
2012-06-04 4:06 ` Doug Evans
2012-06-04 15:03 ` Pedro Alves [this message]
2012-06-19 0:58 ` Doug Evans
2012-07-19 9:18 ` Andreas Schwab
2012-07-30 17:29 ` dje
2012-07-31 7:19 ` Sergio Durigan Junior
2012-08-01 5:18 ` Sergio Durigan Junior
2012-08-01 19:30 ` dje
2012-05-25 10:04 ` Matt Rice
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=4FCCCE27.2060804@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=ratmice@gmail.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