This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH][AArch64] Fix libstdc++ ABI baseline for aarch64-linux-gnu
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Maxim Kuvyrkov <maxim dot kuvyrkov at linaro dot org>
- Cc: 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: Mon, 20 Apr 2015 15:27:30 +0200
- 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>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Mon, Apr 20, 2015 at 04:23:17PM +0300, Maxim Kuvyrkov wrote:
> I have been trying to figure out why I constantly get 2 extra TLS symbols in my aarch64-linux-gnu libstdc++ ABI tests, and it turned out to be due to support for non-TLS toolchain -- as discussed here [*].
> However, as far as I understand, aarch64-linux-gnu postdates NPTL implementation, so I'm wondering if --disable-tls is even applicable to aarch64-linux-gnu. If --disable-tls is not applicable, then we might as well include TLS symbols into aarch64-linux-gnu libstdc++ ABI baseline (as done for solaris configs).
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.
Treating aarch64-linux differently than all the other architectures sounds
wrong to me.