On Fri, 6 Apr 2018, Jonathan Wakely wrote:
> On 6 April 2018 at 12:48, Jonathan Wakely wrote:
> > Currently --with-default-libstdcxx-abi doesn't alter the ABI of the
> > shared lib when the dual-abi is enabled, just whether the initial
> > value of the macro is 0 or 1. All the symbols in the libra
On 6 April 2018 at 12:48, Jonathan Wakely wrote:
> Currently --with-default-libstdcxx-abi doesn't alter the ABI of the
> shared lib when the dual-abi is enabled, just whether the initial
> value of the macro is 0 or 1. All the symbols in the library, and the
> type of exception thrown, are the same
On 6 April 2018 at 12:22, Richard Biener wrote:
> On Fri, 6 Apr 2018, Jonathan Wakely wrote:
>
>> On 6 April 2018 at 10:39, Richard Biener wrote:
>> >
>> > The following allows people configuring the gcc-4 compatible ABI
>> > as the default ABI to retain compatibility with old programs
>> > catchin
On Fri, 6 Apr 2018, Jonathan Wakely wrote:
> On 6 April 2018 at 10:39, Richard Biener wrote:
> >
> > The following allows people configuring the gcc-4 compatible ABI
> > as the default ABI to retain compatibility with old programs
> > catching ios_base::failure by matching the abi version thrown
>
On 6 April 2018 at 10:39, Richard Biener wrote:
>
> The following allows people configuring the gcc-4 compatible ABI
> as the default ABI to retain compatibility with old programs
> catching ios_base::failure by matching the abi version thrown
> to the configured default ABI.
>
> This doesn't reall
