From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, hjl@lucon.org, kettenis@chello.nl
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: FYI: A new C++ demangler
Date: Thu, 10 Jul 2003 21:57:00 -0000 [thread overview]
Message-ID: <200307102157.h6ALvAnl015010@duracef.shout.net> (raw)
Andrew C writes:
> HJ, as a start why not separate out and submit these new tests you
> refered to? Knowing what's broken is a good starting point.
That part is already committed. The libiberty test suite has 64 new
tests. The current demangler fails 31 of the new tests. I saw this in
my test bed and wrote it up. Check out the "Libiberty Testing" section
near the top of:
http://sources.redhat.com/ml/gdb-testers/2003-q3/msg00003.html
To me, the issue of what languages are acceptable for implementing the
demangler is separate from the issue of how the new demangler behaves
versus the old demangler. I can say something about the second issue.
I see that the new demangler does perfectly on all the new tests in
libiberty, and I'm running gdb tests now. I'll have more info to report
in a couple of hours.
Michael C
next reply other threads:[~2003-07-10 21:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 21:57 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2003-07-11 0:36 Michael Elizabeth Chastain
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 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
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
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=200307102157.h6ALvAnl015010@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=kettenis@chello.nl \
/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