From: Mason <slash.tmp@free.fr>
To: GCC help <gcc-help@gcc.gnu.org>
Subject: Re: gcc5 and std::string
Date: Mon, 14 Sep 2015 07:23:00 -0000 [thread overview]
Message-ID: <55F67602.1040401@free.fr> (raw)
In-Reply-To: <55F2D60E.8060707@cloudius-systems.com>
On 11/09/2015 15:24, Avi Kivity wrote:
> This post explains it:
> http://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/
It is quite unfortunate that both C11 and C++11 were published in 2011.
As it is, I thought the above link discussed a change to the C ABI...
"GCC5 and the C++11 ABI"
The author should use c++11 or cxx11 in the URL name.
Regards.
prev parent reply other threads:[~2015-09-14 7:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 13:04 PICCA Frederic-Emmanuel
2015-09-11 13:24 ` Avi Kivity
2015-09-11 13:27 ` Jonathan Wakely
2015-09-11 13:50 ` PICCA Frederic-Emmanuel
2015-09-11 13:55 ` gcc5 " David Abdurachmanov
2015-09-11 13:59 ` PICCA Frederic-Emmanuel
2015-09-11 14:23 ` gcc5 " Jonathan Wakely
2015-09-11 14:33 ` Jonathan Wakely
2015-09-12 9:12 ` PICCA Frederic-Emmanuel
2015-09-12 10:12 ` gcc5 " Jonathan Wakely
2015-09-12 10:42 ` PICCA Frederic-Emmanuel
2015-09-13 6:22 ` PICCA Frederic-Emmanuel
2015-09-14 7:23 ` Mason [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=55F67602.1040401@free.fr \
--to=slash.tmp@free.fr \
--cc=gcc-help@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).