This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Prohibit enum <-> int mixup
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Ian Lance Taylor <iant at google dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Tue, 1 Feb 2011 00:31:31 +0000
- Subject: Re: Prohibit enum <-> int mixup
- References: <20110129164124.GA27641@nibiru.local> <mcr39obpn8r.fsf@google.com> <20110129204856.GA29226@nibiru.local> <AANLkTi=1eim813RowJe0gya19nemWZPeLp_AwiZucU0S@mail.gmail.com> <AANLkTimua1k+ZkEBgEibggvSMDjiP4+sBgGwNj0moS_b@mail.gmail.com> <20110130201121.GD29226@nibiru.local> <AANLkTinKOkAEfyPyFTbtjtUEe9MvM-AoX7n3ZjCoCvK1@mail.gmail.com> <20110130203231.GE29226@nibiru.local> <AANLkTiktVX2NhxEgWfzXV+QE5bjn0gLVe8OgLz_zzobq@mail.gmail.com> <mcrpqrckhoj.fsf@google.com> <AANLkTin9sTnKYGOd8PFrRPncihTZZxQNybro4qNqtrwr@mail.gmail.com> <mcrsjw8iq4m.fsf@google.com>
On 31 January 2011 23:56, Ian Lance Taylor wrote:
> Jonathan Wakely <jwakely.gcc@gmail.com> writes:
>
>> On 31 January 2011 19:16, Ian Lance Taylor wrote:
>>>
>>> Using -std=c++0x will cause libstdc++ to build in C++0x mode, which last
>>> time I checked was not strictly ABI compatible with libstdc++ not built
>>> in C++0x mode. ?So if you link with a dynamic libstdc++.so, you may get
>>> in trouble in some complex scenarios.
>>
>> Do you remember the details? ?I thought we'd done a good job of not
>> breaking the ABI, and have avoided making some changes required by
>> C+0x because they change the ABI. ?I'd like to document the potential
>> problems if you can remember where the incompatibilities are.
>
> http://gcc.gnu.org/PR45093
Aha, thanks