Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] always use demangled name to set scope
Date: Fri, 13 Jun 2003 01:01:00 -0000	[thread overview]
Message-ID: <ro1r85yg593.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030612231727.GA19870@nevyn.them.org>

On Thu, 12 Jun 2003 19:17:27 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> On Thu, Jun 12, 2003 at 03:26:34PM -0700, David Carlton wrote:

>> OK to commit?

> Yes.

Thanks, committed.

> By 6.1 I want to rip out all uses of the demangled name along the
> DWARF-2 code path though.  If I can find the time...

We'll see.  I do think that the nested type deduction machinery is
both useful and impossible to do without demangled names.  And there
are fun bits like how gnuv3_rtti_type looks at the demangled name of
the vtable.  If it were possible to get rid of that, I would be a
happy person indeed, since its existence is probably going to force me
to change the demangler's output somewhat.  (On the other hand, that
call is also a useful canary in the coal mine, too, because of the
RTTI warning that comes out of it.)

But I really am getting a pretty good feel for how to use the
hierarchical info in DWARF to help us here.  And people at Kealia have
given me some very useful bug reports along those lines: this would be
impossible to get at all right without a large C++ code base to
trigger all sorts of random GCC idiosyncracies.

David Carlton
carlton@math.stanford.edu


  reply	other threads:[~2003-06-13  1:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-12 22:26 David Carlton
2003-06-12 23:18 ` Daniel Jacobowitz
2003-06-13  1:01   ` David Carlton [this message]
2003-06-13  4:22     ` Daniel Jacobowitz
2003-06-13  4:28       ` David Carlton
2003-06-13  4:38         ` Daniel Jacobowitz
2003-06-13 18:53           ` David Carlton
2003-06-13 18:56             ` Daniel Jacobowitz
2003-06-13 19:01               ` 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=ro1r85yg593.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.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