From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH to handling of exception specs in system headers
Date: Tue, 02 Jun 2015 14:19:00 -0000 [thread overview]
Message-ID: <yddwpzmmc88.fsf@lokon.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <556C90E9.8010204@redhat.com> (Jason Merrill's message of "Mon, 01 Jun 2015 13:05:45 -0400")
Jason Merrill <jason@redhat.com> writes:
> On 06/01/2015 11:34 AM, Rainer Orth wrote:
>> Isn't this about global vs. std namespace?
>
> Probably. Does making the declaration in the testcase extern "C" help?
It does indeed, and the test still passes on Linux.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2015-06-02 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 20:59 Jason Merrill
2015-06-01 12:13 ` Rainer Orth
2015-06-01 14:58 ` Jason Merrill
2015-06-01 15:34 ` Rainer Orth
2015-06-01 17:05 ` Jason Merrill
2015-06-02 14:19 ` Rainer Orth [this message]
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=yddwpzmmc88.fsf@lokon.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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).