From: Eric Botcazou <ebotcazou@adacore.com>
To: Michael Matz <matz@suse.de>
Cc: Richard Guenther <richard.guenther@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: Mark objects death at end of scope
Date: Thu, 03 Nov 2011 14:33:00 -0000 [thread overview]
Message-ID: <201111031522.58602.ebotcazou@adacore.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1111031407410.30317@wotan.suse.de>
> libcpp and libcommon and libcommon-target, the latter are:
>
> diagnostic.o pretty-print.o intl.o input.o version.o
> prefix.o params.o opts.o opts-common.o options.o vec.o hooks.o
> common/common-targhooks.o
> <target>-common.o
>
> Doesn't read as if these were good candidates to compile with C only when
> the rest is C++.
Yes, compiling everything with -fno-exceptions seems by far the simplest route.
--
Eric Botcazou
next prev parent reply other threads:[~2011-11-03 14:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 0:05 Michael Matz
2011-11-03 1:21 ` Eric Botcazou
2011-11-03 9:24 ` Richard Guenther
2011-11-03 10:26 ` Eric Botcazou
2011-11-03 12:52 ` Richard Guenther
2011-11-03 13:42 ` Michael Matz
2011-11-03 14:33 ` Eric Botcazou [this message]
2011-11-03 14:46 ` Michael Matz
2011-11-03 14:55 ` Eric Botcazou
2011-11-03 14:23 ` Build gcc/ with -fno-exceptions -fno-rtti Michael Matz
2011-11-03 14:26 ` Paolo Bonzini
2011-11-03 14:31 ` Richard Guenther
2011-11-03 15:08 ` Eric Botcazou
2011-11-03 17:46 ` Michael Matz
2011-11-03 9:59 ` Mark objects death at end of scope Richard Guenther
2011-11-03 11:07 ` Michael Matz
2011-11-07 16:05 ` Michael Matz
2011-11-07 22:10 ` Richard Guenther
2011-11-10 23:57 ` Steve Ellcey
2011-11-11 15:32 ` Michael Matz
2011-11-11 16:20 ` Mark objects death@end " Ulrich Weigand
2011-11-11 17:22 ` Michael Matz
2011-11-11 17:45 ` Ulrich Weigand
2011-11-11 17:45 ` Michael Matz
2011-11-03 10:57 ` Mark objects death at end " Jakub Jelinek
2011-11-03 11:57 ` Michael Matz
2011-11-03 12:47 ` Jakub Jelinek
2011-11-03 13:14 ` Michael Matz
2011-11-04 12:28 ` Jakub Jelinek
2011-11-04 12:45 ` Jakub Jelinek
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=201111031522.58602.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
--cc=richard.guenther@gmail.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).