From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] always use demangled name to set scope
Date: Fri, 13 Jun 2003 04:38:00 -0000 [thread overview]
Message-ID: <20030613043834.GA24239@nevyn.them.org> (raw)
In-Reply-To: <ro1brx2lhya.fsf@jackfruit.Stanford.EDU>
On Thu, Jun 12, 2003 at 09:28:13PM -0700, David Carlton wrote:
> On Fri, 13 Jun 2003 00:22:14 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> > On Thu, Jun 12, 2003 at 06:01:28PM -0700, David Carlton wrote:
> >> On Thu, 12 Jun 2003 19:17:27 -0400, Daniel Jacobowitz <drow@mvista.com> said:
>
> >> > 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
>
> > I completely disagree. We have all the machinery in DWARF-2 to do it
> > without demangled names by using the available hierarchy; it was
> > designed to suffice for this.
>
> Yeah, but we need DW_TAG_namespace to do it, and a version of GCC
> providing that probably won't be released until next calendar year. I
> certainly don't use demangled names to do nested type deduction if we
> have DW_TAG_namespace, but I do think it will be important for the
> next two or three years.
That's namespace deduction. Nested type deduction is a slightly
different story - the principle is the same but we already have all the
information we need.
> >> 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.)
>
> > I am fairly sure we can kill that for DWARF-2 at least.
>
> Sounds good to me.
I just hope I'm right :)
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-13 4:38 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
2003-06-13 4:22 ` Daniel Jacobowitz
2003-06-13 4:28 ` David Carlton
2003-06-13 4:38 ` Daniel Jacobowitz [this message]
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=20030613043834.GA24239@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@math.stanford.edu \
--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