From: "H. J. Lu" <hjl@lucon.org>
To: David Carlton <carlton@kealia.com>
Cc: binutils@sources.redhat.com, GDB <gdb@sources.redhat.com>
Subject: Re: FYI: A new C++ demangler
Date: Thu, 10 Jul 2003 15:36:00 -0000 [thread overview]
Message-ID: <20030710153608.GA26615@lucon.org> (raw)
In-Reply-To: <yf265maz9i9.fsf@hawaii.kealia.com>
On Thu, Jul 10, 2003 at 08:28:30AM -0700, David Carlton wrote:
> On Thu, 10 Jul 2003 07:35:57 -0700, "H. J. Lu" <hjl@lucon.org> said:
>
> > I will put a new C++ demangler in Linux binutils, which should fix all
> > known bugs in the old demangler.
>
> Just to clarify: is the output of the new demangler exactly the same
> as the output of the old demangler in all cases where the old
> demangler is correct? Because if the new demangler does go into the
> mainline libiberty, GDB will care about the details of its output.
There is a demangler testsuite in libiberty and I added a few new
tests which are failed with the old demangler. The new demangler
passed all of them. I assume the outputs must be the same.
BTW, I am not sure when/if the new demangler will show up in mainline
libiberty. That is why I am putting it in my Linux binutils. People
can also apply it to their own gdb source to get a better demangler.
H.J.
next prev parent reply other threads:[~2003-07-10 15:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 14:36 H. J. Lu
2003-07-10 14:40 ` Ian Lance Taylor
2003-07-10 14:54 ` H. J. Lu
2003-07-10 15:28 ` David Carlton
2003-07-10 15:36 ` H. J. Lu [this message]
2003-07-10 15:44 ` David Carlton
2003-07-10 20:57 ` Mark Kettenis
2003-07-10 21:17 ` Andrew Cagney
2003-07-10 21:44 ` H. J. Lu
2003-07-10 22:58 ` Frank Ch. Eigler
2003-07-10 23:19 ` Andrew Cagney
2003-07-10 21:22 ` DJ Delorie
2003-07-10 15:42 Michael Elizabeth Chastain
2003-07-10 15:51 ` H. J. Lu
2003-07-10 16:38 ` Ian Lance Taylor
2003-07-10 21:57 Michael Elizabeth Chastain
2003-07-11 0:36 Michael Elizabeth Chastain
2003-07-12 18:02 Nathanael Nerode
2003-07-15 16:17 ` Andrew Cagney
2003-07-15 18:03 ` Gabriel Dos Reis
2003-07-15 19:02 ` Andrew Cagney
2003-07-15 19:03 ` Alexandre Oliva
2003-07-15 19:16 ` H. J. Lu
2003-07-15 19:49 ` Alexandre Oliva
2003-07-15 19:55 ` H. J. Lu
2003-07-15 22:30 ` Alexandre Oliva
2003-07-15 23:14 ` H. J. Lu
2003-07-16 2:31 ` Alexandre Oliva
2003-07-16 3:21 ` Ian Lance Taylor
2003-07-16 17:12 ` Nathanael Nerode
2003-07-15 19:16 ` Ian Lance Taylor
2003-07-15 19:23 ` H. J. Lu
2003-07-15 20:05 ` DJ Delorie
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=20030710153608.GA26615@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=carlton@kealia.com \
--cc=gdb@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