PATCH: Support the new demangler written in C++

Alexandre Oliva aoliva@redhat.com
Tue Jul 8 05:42:00 GMT 2003


On Jul  8, 2003, Nathanael Nerode <neroden@twcny.rr.com> wrote:

> 2. Make the demangler part of libstdc++-v3.

This won't help binutils or gdb.  libstdc++-v3 is not build for the
host.

> 4. Make the C++ demangler totally independent of libstdc++-v3 so that it 
> can be compiled with a freestanding C++ compiler.

I understand this is already the case.  If it wasn't, we couldn't even
think of building the demangler for the build or the host machines.

> Then the C++ demangler can go into libiberty and live there happily,
> and replace both of the existing ones.

Nope.  The problem is that a freestanding...  Oh, wait.  You mean
freestanding as in no C++ library.  Well, this happens to be the case
already.  The demangler doesn't need the C++ library linked in, it
just needs its headers, for some templates it uses.  As I wrote
before, I *think* it would work for the demangler to require
libstdc++-v3 to have already been *configured*, even if not yet
*built*.

But this only solves the problem for target libraries.  We still have
a new requirement for build (although I don't see why we'd be building
a C++ demangler for the build environment) and the host (where
binutils and gdb need the demangler).

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer



More information about the Gcc-patches mailing list