This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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: New demangler in C++

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Mark Mitchell <mark at codesourcery dot com>
Cc: gdr at integrable-solutions dot net, libstdc++ at gcc dot gnu dot org
Date: Thu, 27 Feb 2003 11:30:34 -0600
Subject: Re: New demangler in C++
References: <1046136428.11789.227.camel@doubledemon.codesourcery.com><m3smuchj86.fsf@uniton.integrable-solutions.net><20030227111358.02dbfc57.bkoz@redhat.com><1046366611.3939.24.camel@doubledemon.codesourcery.com>

>If the new version is better we should use it -- but better should
>include the fact that it can truly replace the old version.  

I disagree on this critieria. I think we'll just have to disagree on
this issue.

>Is it just in V3 or in libiberty as well?

Does libiberty have __cxa_demangle? 

(No.) 

Again, this is just a replacement for __cxa_demangle, the v3 demangler
as specified by the IA 64 C++ ABI, not the uber-demangler as used in
libiberty that tries to do v2, v3, hp, lucid, arm, java etc.

-benjamin

Follow-Ups:
- Re: New demangler in C++
  - From: Mark Mitchell

References:
- New demangler in C++
  - From: Mark Mitchell
- Re: New demangler in C++
  - From: Gabriel Dos Reis
- Re: New demangler in C++
  - From: Benjamin Kosnik
- Re: New demangler in C++
  - From: Mark Mitchell

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