From: Daniel Jacobowitz <drow@false.org>
To: Keith Seitz <keiths@redhat.com>,
Michael Eager <eager@eagercon.com>,
gdb-patches@sourceware.org
Subject: Re: [RFA] dwarf2_physname
Date: Tue, 01 Sep 2009 22:27:00 -0000 [thread overview]
Message-ID: <20090901222725.GA26894@caradoc.them.org> (raw)
In-Reply-To: <20090901221122.GA24658@caradoc.them.org>
On Tue, Sep 01, 2009 at 06:11:22PM -0400, Daniel Jacobowitz wrote:
> I assume this patch is a distant descendant of the one I sent you a
> while back. Is its goal to create a useful name for each symbol, or
> to match the one produced by some other source - probably the
> demangler? What sort of template cases have you looked at?
I guess the big picture is that I want to know how these pieces fit
together, before trying to figure out if each individual piece is
right. It's a hack (IMO!) that we need to generate physnames - but
it may be the only practical path which is how I ended up there myself
:-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-09-01 22:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 22:51 Keith Seitz
2009-08-31 23:10 ` Michael Eager
2009-08-31 23:23 ` Keith Seitz
2009-08-31 23:35 ` Michael Eager
2009-09-01 22:11 ` Daniel Jacobowitz
2009-09-01 22:27 ` Daniel Jacobowitz [this message]
2009-09-01 23:18 ` Michael Eager
2009-09-01 23:37 ` Daniel Jacobowitz
2009-09-02 1:12 ` Michael Eager
2009-09-01 23:26 ` Keith Seitz
2009-09-01 23:42 ` Daniel Jacobowitz
2009-09-14 18:39 ` Keith Seitz
2009-09-14 22:48 ` Daniel Jacobowitz
2009-09-14 23:56 ` Keith Seitz
2009-09-15 13:32 ` Daniel Jacobowitz
2009-09-15 15:53 ` Keith Seitz
2009-09-15 16:12 ` Daniel Jacobowitz
2009-09-16 20:27 ` Keith Seitz
2009-09-18 22:34 ` Tom Tromey
[not found] ` <m37hwjy2tl.fsf@fleche.redhat.com>
2009-09-01 0:06 ` Michael Eager
2009-09-01 21:27 ` Tom Tromey
2009-09-01 22:10 ` Keith Seitz
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=20090901222725.GA26894@caradoc.them.org \
--to=drow@false.org \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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