This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][AArch64] Fix libstdc++ ABI baseline for aarch64-linux-gnu
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Maxim Kuvyrkov <maxim dot kuvyrkov at linaro dot org>, Andreas Schwab <schwab at redhat dot com>, Marcus Shawcroft <marcus dot shawcroft at arm dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 28 Apr 2015 23:14:26 +0000
- Subject: Re: [PATCH][AArch64] Fix libstdc++ ABI baseline for aarch64-linux-gnu
- Authentication-results: sourceware.org; auth=none
- References: <DDC1258C-CC1F-4347-ADFA-2C74659AA012 at linaro dot org> <20150420132730 dot GI1725 at tucnak dot redhat dot com>
On Mon, 20 Apr 2015, Jakub Jelinek wrote:
> If you want to do anything about it, instead hack up the ABI list checker,
> so that for configurations with disabled TLS it ignores TLS symbols in the
> ABI list, then they can be added on all architectures.
Is anyone actually using current GCC for non-TLS configurations of glibc
versions so old as to support it (2.3 and earlier?), and does current
libstdc++ actually build with such old glibc? If they are, it seems to me
like it should be for the people doing so to implement the conditional
handling of TLS in these tests if they want them to pass; the baselines
should have what's right for normal configurations (i.e. including TLS).
(There may well be people using non-glibc libraries such as uClibc without
TLS, but I'd expect those to need separate baselines anyway because of
e.g. locale differences.)
--
Joseph S. Myers
joseph@codesourcery.com