Re: FYI: A new C++ demangler

["H. J. Lu" <hjl@lucon.org>]

[-- Attachment #1: Type: text/plain, Size: 785 bytes --]

On Thu, Jul 10, 2003 at 11:42:55AM -0400, Michael Elizabeth Chastain wrote:
> I will throw the new demangler on my gdb test bed and look for regressions.
> I'm sure H. J. has the demangler test suite covered and I can do the
> gdb test suite.
> 
> I have kind of a silly question.  Do I need to rebuild binutils and/or gcc
> with the new demangler, or can I just rebuild gdb?  That is, do gcc or
> binutils ever need to run the demangler while compiling?

You only need to rebuild gdb with it unless you need to use c++filt,
which is the part of binutils.

I am enclosing 2 files. README is used to apply my patch and recreate
those generated files. I also included a correct patch for binutils/gdb
since now the toplevel directories are different between binutils/gdb
and gcc.


H.J.

[-- Attachment #2: README --]
[-- Type: text/plain, Size: 349 bytes --]

#! /bin/sh

dir=`dirname $0`

patch -p1 -b --suffix .demangler < $dir/src-demangler-11.patch && \
true
[ $? = 0 ] || exit 1
(cd demangler && sh ./bootstrap)
[ $? = 0 ] || exit 1
(cd libiberty && rm -f configure && autoconf-2.13)
[ $? = 0 ] || exit 1
rm -f configure && autoconf-2.13 && rm -f Makefile.in && autogen Makefile.def
[ $? = 0 ] || exit 1

[-- Attachment #3: src-demangler-11.patch.gz.bz2 --]
[-- Type: application/x-bzip2, Size: 29324 bytes --]