This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: C++ demangling of 64-bit symbols on ppc64

From: Ian Lance Taylor <iant at google dot com>
To: Maynard Johnson <maynardj at us dot ibm dot com>
Cc: binutils at sourceware dot org
Date: 05 Apr 2007 17:55:03 -0700
Subject: Re: C++ demangling of 64-bit symbols on ppc64
References: <4612D2FA.4050407@us.ibm.com> <m3abxn3a3r.fsf@localhost.localdomain> <4614F52E.3070606@us.ibm.com> <m3mz1m24na.fsf@localhost.localdomain> <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

References:
- C++ demangling of 64-bit symbols on ppc64
  - From: Maynard Johnson
- Re: C++ demangling of 64-bit symbols on ppc64
  - From: Ian Lance Taylor
- Re: C++ demangling of 64-bit symbols on ppc64
  - From: Maynard Johnson
- Re: C++ demangling of 64-bit symbols on ppc64
  - From: Ian Lance Taylor
- Re: C++ demangling of 64-bit symbols on ppc64
  - From: Maynard Johnson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]