From: Jonathan Wakely <jwakely@redhat.com>
To: Federico Lenarduzzi <federico.lenarduzzi@tallertechnologies.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Fix exceptions being generated when compiling with -fno-exceptions
Date: Wed, 15 Apr 2015 14:56:00 -0000 [thread overview]
Message-ID: <20150415145556.GT9755@redhat.com> (raw)
In-Reply-To: <CAGVZXp9vUV801HGVV9ekC4xfH671UUWJ9=MTwbb8iVDMsHzrfg@mail.gmail.com>
On 15/04/15 11:15 -0300, Federico Lenarduzzi wrote:
>The idea of this patch is that using this function not depends from a
>configuration
>flag but depends of a flag which participates in the selection of the
>correct multilib.
OK, then I agree it's better to make it conditional on
__cpp_exceptions which can have different values for your different
multilibs, whereas _GLIBCXX_VERBOSE would be the same in all of them.
I have no objections to the change.
next prev parent reply other threads:[~2015-04-15 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 14:15 Federico Lenarduzzi
2015-04-15 14:56 ` Jonathan Wakely [this message]
2015-04-16 14:21 ` Federico Lenarduzzi
2015-04-16 14:33 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2015-04-14 15:18 Federico Lenarduzzi
2015-04-14 19:27 ` Jonathan Wakely
2015-04-27 21:06 ` Jonathan Wakely
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=20150415145556.GT9755@redhat.com \
--to=jwakely@redhat.com \
--cc=federico.lenarduzzi@tallertechnologies.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
/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).