From: Ian Lance Taylor <iant@google.com>
To: Maynard Johnson <maynardj@us.ibm.com>
Cc: binutils@sourceware.org
Subject: Re: C++ demangling of 64-bit symbols on ppc64
Date: Fri, 06 Apr 2007 00:55:00 -0000 [thread overview]
Message-ID: <m38xd6z5i0.fsf@localhost.localdomain> (raw)
In-Reply-To: <46154B16.9060500@us.ibm.com>
Maynard Johnson <maynardj@us.ibm.com> writes:
> >Or, we could change the interface to the demangler. I don't think it
> >would be appropriate for the demangler to unconditionally remove
> >
> Why? Are there some circumstances where the correct answer is
> returned, even if the symbol has leading dots?
I believe the demangler should by default strive to avoid converting
two different mangled symbol names to the same demangled string. When
it does so, the output of nm --demangle becomes confusing.
Ian
prev parent reply other threads:[~2007-04-06 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 22:19 Maynard Johnson
2007-04-05 1:04 ` Ian Lance Taylor
2007-04-05 13:10 ` Maynard Johnson
2007-04-05 16:00 ` Ian Lance Taylor
2007-04-05 19:16 ` Maynard Johnson
2007-04-06 0:55 ` Ian Lance Taylor [this message]
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=m38xd6z5i0.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=maynardj@us.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).