This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: _GLIBCXX_ASYNC_ABI_COMPAT and ~_Async_state_common()

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: Maxim Yegorushkin <maxim dot yegorushkin at gmail dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Tue, 2 Oct 2012 15:32:41 +0100
Subject: Re: _GLIBCXX_ASYNC_ABI_COMPAT and ~_Async_state_common()
References: <CAMg=2zJ5WooUc2Y5+__U5uGWYHCmHzuwXyRNciR8fk4gEui_zQ@mail.gmail.com> <CAH6eHdSUBZ-zG-oveuho_dovRvRWbO=5d00YySznJh4ZTCk=fA@mail.gmail.com> <CAMg=2z+UJ+J-Tet2HJvx044WS64--fBLhEseH_cfbxSEurA6ng@mail.gmail.com>

On 2 October 2012 12:40, Maxim Yegorushkin wrote:
> Thanks for the reply Jon,
>
> It would be nice to be able to build gcc-4.7.2 without maintaining
> binary compatibility with previous versions of gcc-4.7 since, for
> example, I like to recompile the whole codebase when switching to a
> newer version of a compiler just to eliminate any uncertainty arising
> from possible binary ABI compatibility issues. Something like
> --no-legacy-abi configure switch.

Hmm, yes, I can see that being useful for a subset of users - but note
that in theory you might need to recompile your entire distro. If you
link to any system libs that were built with an older GCC they might
have references to legacy ABI symbols in libstdc++.so.

References:
- _GLIBCXX_ASYNC_ABI_COMPAT and ~_Async_state_common()
  - From: Maxim Yegorushkin
- Re: _GLIBCXX_ASYNC_ABI_COMPAT and ~_Async_state_common()
  - From: Jonathan Wakely
- Re: _GLIBCXX_ASYNC_ABI_COMPAT and ~_Async_state_common()
  - From: Maxim Yegorushkin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]