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: analysis of libiberty/cp-demangle.c for libsupc++/__cxa_demangle

From: Mark Mitchell <mark at codesourcery dot com>
To: Ian Lance Taylor <ian at wasabisystems dot com>
Cc: Benjamin Kosnik <bkoz at redhat dot com>, libstdc++ at gcc dot gnu dot org
Date: Mon, 23 Feb 2004 17:34:19 -0800
Subject: Re: analysis of libiberty/cp-demangle.c for libsupc++/__cxa_demangle
Organization: CodeSourcery, LLC
References: <20040223170416.7a0ab854.bkoz@redhat.com> <m3wu6dgtqe.fsf@gossamer.airs.com>

Ian Lance Taylor wrote:

Benjamin Kosnik <bkoz@redhat.com> writes:
So by my reading, when given something like _X11TransParseAddress
which is not a valid mangled name, it is correct for __cxa_demangle()
to return NULL with status set to -2.

What other reading could there be?

The ABI implies that you can feed an 'extern "C"' name to __cxa_demangle.

For example, it says that "i" should be demangled as "i".

It's hard (for me) to see how to get that without considering "i" a valid mangled name.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

Follow-Ups:
- Re: analysis of libiberty/cp-demangle.c for libsupc++/__cxa_demangle
  - From: Ian Lance Taylor

References:
- analysis of libiberty/cp-demangle.c for libsupc++/__cxa_demangle
  - From: Benjamin Kosnik
- Re: analysis of libiberty/cp-demangle.c for libsupc++/__cxa_demangle
  - From: Ian Lance Taylor

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