From: Ian Lance Taylor <ian@airs.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: carlton@kealia.com, hjl@lucon.org, binutils@sources.redhat.com,
gdb@sources.redhat.com
Subject: Re: FYI: A new C++ demangler
Date: Thu, 10 Jul 2003 16:38:00 -0000 [thread overview]
Message-ID: <m3of0272ws.fsf@gossamer.airs.com> (raw)
In-Reply-To: <200307101542.h6AFgtuY009713@duracef.shout.net>
Michael Elizabeth Chastain <mec@shout.net> writes:
> 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?
Some of the binutils are linked against the demangler. This doesn't
matter for compilation, only for error reporting and for the output of
objdump and nm. I don't know whether this matters for your test bed.
Ian
next prev parent reply other threads:[~2003-07-10 16:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 15:42 Michael Elizabeth Chastain
2003-07-10 15:51 ` H. J. Lu
2003-07-10 16:38 ` Ian Lance Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-12 18:02 Nathanael Nerode
2003-07-15 16:17 ` Andrew Cagney
2003-07-15 18:03 ` Gabriel Dos Reis
2003-07-15 19:02 ` Andrew Cagney
2003-07-15 19:03 ` Alexandre Oliva
2003-07-15 19:16 ` H. J. Lu
2003-07-15 19:49 ` Alexandre Oliva
2003-07-15 19:55 ` H. J. Lu
2003-07-15 22:30 ` Alexandre Oliva
2003-07-15 23:14 ` H. J. Lu
2003-07-16 2:31 ` Alexandre Oliva
2003-07-16 3:21 ` Ian Lance Taylor
2003-07-16 17:12 ` Nathanael Nerode
2003-07-15 19:16 ` Ian Lance Taylor
2003-07-15 19:23 ` H. J. Lu
2003-07-15 20:05 ` DJ Delorie
2003-07-11 0:36 Michael Elizabeth Chastain
2003-07-10 21:57 Michael Elizabeth Chastain
2003-07-10 14:36 H. J. Lu
2003-07-10 14:40 ` Ian Lance Taylor
2003-07-10 14:54 ` H. J. Lu
2003-07-10 15:28 ` David Carlton
2003-07-10 15:36 ` H. J. Lu
2003-07-10 15:44 ` David Carlton
2003-07-10 20:57 ` Mark Kettenis
2003-07-10 21:17 ` Andrew Cagney
2003-07-10 21:44 ` H. J. Lu
2003-07-10 22:58 ` Frank Ch. Eigler
2003-07-10 23:19 ` Andrew Cagney
2003-07-10 21:22 ` DJ Delorie
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=m3of0272ws.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=binutils@sources.redhat.com \
--cc=carlton@kealia.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=mec@shout.net \
/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).