From: "H. J. Lu" <hjl@lucon.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Gabriel Dos Reis <gdr@integrable-solutions.net>,
Andrew Cagney <ac131313@redhat.com>,
Nathanael Nerode <neroden@twcny.rr.com>,
fche@redhat.com, gdb@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: FYI: A new C++ demangler
Date: Tue, 15 Jul 2003 19:55:00 -0000 [thread overview]
Message-ID: <20030715195522.GA21667@lucon.org> (raw)
In-Reply-To: <orisq38tak.fsf@free.redhat.lsd.ic.unicamp.br>
On Tue, Jul 15, 2003 at 04:49:07PM -0300, Alexandre Oliva wrote:
> On Jul 15, 2003, "H. J. Lu" <hjl@lucon.org> wrote:
>
> > FWIW, my C++ demangler patch needs $(CXX) to compile, only $(CC) to
> > link.
>
> This may be the case with the current GCC, but other C++ compilers,
> and future versions of GCC (especially after we introduce support for
> `export'ed templates) may very well introduce dependencies on their
> run-time libraries, requiring linking with them and possibly even
> using their C++ compiler driver to link.
The demangler configure tests if $(CC) can be used for linking. If not,
the new C++ demangler won't be used. The new C++ demangler is compiled
with -fno-rtti -fno-exceptions for libiberty. I hope when the new
features are added to gcc, there is an option to disable it if needed.
H.J.
next prev parent reply other threads:[~2003-07-15 19:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
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: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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-07-11 0:36 Michael Elizabeth Chastain
2003-07-10 21:57 Michael Elizabeth Chastain
2003-07-10 15:43 Michael Elizabeth Chastain
2003-07-10 15:51 ` H. J. Lu
2003-07-10 16:38 ` Ian Lance Taylor
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=20030715195522.GA21667@lucon.org \
--to=hjl@lucon.org \
--cc=ac131313@redhat.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=fche@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=gdr@integrable-solutions.net \
--cc=neroden@twcny.rr.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).