RFC: Make a standalone GNU V3 C++ demangler

[H. J. Lu]

On Thu, Apr 24, 2003 at 11:04:45AM -0400, DJ Delorie wrote:
> 
> > This patch provides a more accurate C++ demangler for libiberty to use,
> > if certain requirements can be met (g++, <vector>). If it can't, the old
> > one is used instead. Therefore, there will be no added dependency for gdb
> > or binutils.
> 
> The build dependency is a little strange, though.  Libiberty has to go
> before binutils, binutils before gcc, gcc before libstdc++, libstdc++
> before demangler, and demangler before binutils and gdb.
> 
> We might as well just put the new demangler in libiberty and only
> enable it when we can build it.

I tried and it didn't work for gcc. When you bootstrap gcc natively
with C++ enabled, the C++ compiler with <vector> isn't available before
libstdc++ is finished. As the result, the target libiberty will use the
old demangler. Also if you don't have the C++ compiler installed, the
old demangler will always be used even if you enable C++ in gcc build.
I don't believe that is what we want.


H.J.