From: Jason Merrill <jason@redhat.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>,
Jonathan Wakely <jwakely@redhat.com>
Subject: Re: C++ PATCH for c++/65046 (ABI tags and functions/variables)
Date: Mon, 06 Apr 2015 20:45:00 -0000 [thread overview]
Message-ID: <5522F065.3040807@redhat.com> (raw)
In-Reply-To: <20150406132308.GC392@x4>
On 04/06/2015 09:23 AM, Markus Trippelsdorf wrote:
> The issue is that clang uses the new libstdc++ ABI just fine. And before
> this commit one could switch compilers without any problems...
Hmm, I suppose that when we switched to using inline namespaces for much
of the new ABI, switching compilers became more feasible; now tags are
only used for functions and variables, so you're less likely to run into
a problem, but it could still cause trouble if you use one of the tagged
functions in libstdc++ and get the one returning an old-ABI string. So
I would be nervous about using clang with a dual-ABI libstdc++. Does
clang use the new ABI by default with GCC 5 libstdc++? If it uses the
old ABI then using the un-tagged function names is fine, but we don't
want it to link with code that uses the new ABI.
Jason
next prev parent reply other threads:[~2015-04-06 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 19:17 Jason Merrill
2015-04-04 11:38 ` Markus Trippelsdorf
2015-04-06 12:59 ` Jason Merrill
2015-04-06 13:23 ` Markus Trippelsdorf
2015-04-06 20:45 ` Jason Merrill [this message]
2015-04-06 21:31 ` Markus Trippelsdorf
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=5522F065.3040807@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=markus@trippelsdorf.de \
/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).