From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ken Block To: "H . J . Lu" Cc: Nick Clifton , binutils@sourceware.cygnus.com Subject: Re: New ABI demangler support in binutils Date: Thu, 15 Jun 2000 12:17:00 -0000 Message-id: <39492B9B.D3F368FA@zk3.dec.com> References: <200006151809.LAA18701@elmo.cygnus.com> <20000615120653.A21455@lucon.org> X-SW-Source: 2000-06/msg00275.html Everything would probably be best, but the following is the minimum you can take for the demangler: libiberty/Makefile.in libiberty/cplus-dem.c libiberty/cp-demangle.c (new) libiberty/dyn-string.c (new) libiberty/sort.c (new) include/demangle.h include/sort.h (new) include/dyn-string.h (new) > On Thu, Jun 15, 2000 at 11:09:47AM -0700, Nick Clifton wrote: > > Hi H.J. > > > > : > The demangler support for the new API is available in the libiberty that > > : > comes with GCC, but does not seem to be available in binutils. How does > > : > one go about getting demangler support for the new ABI in binutils? How > > : > is libiberty kept in sync between GCC, gdb, and binutils? > > : > > > : > > : Someone has to sync it. > > > > Correct, althpough there are (tentative) plans to merge the gcc abnd > > binutils repositories at some point in the future. > > > > : Nick, should I give it a try? > > > > Please do. > > > > Should I sync the whole libiberty or just the demangler? I prefer > the whole libiberty since there are quite a few files for demangler > in libiberty and I don't know if they will work right without other > changes. > > H.J.