From: Ken Block <block@zk3.dec.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Nick Clifton <nickc@cygnus.com>, binutils@sourceware.cygnus.com
Subject: Re: New ABI demangler support in binutils
Date: Thu, 15 Jun 2000 12:17:00 -0000 [thread overview]
Message-ID: <39492B9B.D3F368FA@zk3.dec.com> (raw)
In-Reply-To: <20000615120653.A21455@lucon.org>
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.
next prev parent reply other threads:[~2000-06-15 12:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-15 11:16 Nick Clifton
2000-06-15 12:07 ` H . J . Lu
2000-06-15 12:16 ` Nick Clifton
2000-06-15 12:23 ` Ian Lance Taylor
2000-06-15 13:31 ` H . J . Lu
2000-06-15 13:39 ` Ian Lance Taylor
2000-06-15 13:43 ` H . J . Lu
2000-06-17 2:05 ` David O'Brien
2000-06-19 20:04 ` Andrew Cagney
2000-06-15 12:47 ` Chris Faylor
2000-06-15 12:17 ` Ken Block [this message]
2000-06-15 12:34 ` Mark Mitchell
2000-06-15 12:37 ` Ken Block
2000-06-15 12:43 ` Mark Mitchell
2000-06-19 20:02 ` Andrew Cagney
2000-06-19 23:25 ` H . J . Lu
2000-06-15 14:05 ` H . J . Lu
2000-06-15 14:26 ` Chris Faylor
2000-06-15 14:52 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2000-06-15 13:12 Nick Clifton
2000-06-15 12:51 Nick Clifton
2000-06-15 12:57 ` Ian Lance Taylor
2000-06-15 13:01 ` Chris Faylor
2000-06-15 12:48 Nick Clifton
2000-06-15 9:20 Ken Block
2000-06-15 9:29 ` H . J . Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39492B9B.D3F368FA@zk3.dec.com \
--to=block@zk3.dec.com \
--cc=binutils@sourceware.cygnus.com \
--cc=hjl@lucon.org \
--cc=nickc@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).