public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey Yasskin <jyasskin@google.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: gcc@gcc.gnu.org
Subject: Re: Long-term plan for C++98/C++11 incompatibility
Date: Thu, 15 Dec 2011 18:04:00 -0000	[thread overview]
Message-ID: <CANh-dXkYMTYzeYGSxK0oLCuT4za1Z4vnvBZLWj0+-KqQYWVNQQ@mail.gmail.com> (raw)
In-Reply-To: <CAAiZkiC8Rsot+TDPpOxJdUtFcT7GPdk9KimF_z139tCLxJVGaQ@mail.gmail.com>

On Mon, Oct 10, 2011 at 5:07 PM, Gabriel Dos Reis
<gdr@integrable-solutions.net> wrote:
> On Mon, Oct 10, 2011 at 5:25 PM, Joe Buck <Joe.Buck@synopsys.com> wrote:
>> On Fri, Oct 07, 2011 at 07:35:17PM -0700, Gabriel Dos Reis wrote:
>>> C++11 is essentially binary incompatible with C++98.
>>
>> Only partially.  The layout for user-defined classes is the same, and
>
> PODness has changed from C++98.

Sorry for digging this up months later, but this caught my eye. I've
heard several people strongly claim that the core ABI didn't change,
and here you seem to be contradicting them. Can you give a concrete
example of a user-defined class that doesn't use any standard library
features but changes layout between C++98 and C++11 when compiled with
gcc?

Thanks,
Jeffrey

  reply	other threads:[~2011-12-15 18:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 23:44 James Y Knight
2011-10-08  2:17 ` Jonathan Wakely
2011-10-08  2:35   ` Jonathan Wakely
2011-10-08  4:57 ` Gabriel Dos Reis
2011-10-08  6:39   ` Joe Buck
2011-10-08  7:34     ` Gabriel Dos Reis
2011-10-11  9:41       ` Joe Buck
2011-10-11 10:53         ` Gabriel Dos Reis
2011-12-15 18:04           ` Jeffrey Yasskin [this message]
2012-01-05 18:35           ` Jason Merrill
2012-01-05 18:39             ` Jason Merrill
2012-01-05 18:55             ` Joe Buck
2012-01-05 22:23               ` Jason Merrill
2011-10-08  7:35 ` Miles Bader

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=CANh-dXkYMTYzeYGSxK0oLCuT4za1Z4vnvBZLWj0+-KqQYWVNQQ@mail.gmail.com \
    --to=jyasskin@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    /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).