Andreas Schwab writes:
> Jakub Jelinek writes:
>
>> I'd say so, perhaps with the exception of Solaris where I'd leave that to
>> the target maintainer to decide.
>
> Done.
I'd leave them in the solaris2.10 baselines: there are no non-TLS
toolchains there, and I'd rather know if TLS support some
On Thu, Apr 10, 2014 at 10:42:28AM +0200, Andreas Schwab wrote:
> Jakub Jelinek writes:
>
> > I'd say so, perhaps with the exception of Solaris where I'd leave that to
> > the target maintainer to decide.
>
> Done.
>
> > The other alternative is to have the TLS symbols included everywhere and a
Jakub Jelinek writes:
> I'd say so, perhaps with the exception of Solaris where I'd leave that to
> the target maintainer to decide.
Done.
> The other alternative is to have the TLS symbols included everywhere and add
> some magic to the abi checking scripts/proglet which would detect the
> emu
On Thu, Apr 10, 2014 at 10:15:59AM +0200, Andreas Schwab wrote:
> Jakub Jelinek writes:
>
> > On Thu, Apr 10, 2014 at 09:52:35AM +0200, Andreas Schwab wrote:
> >> Tested on ia64-suse-linux and installed as obvious.
> >
> > Please don't add the TLS symbols in there, they aren't included
> > in any
Jakub Jelinek writes:
> On Thu, Apr 10, 2014 at 09:52:35AM +0200, Andreas Schwab wrote:
>> Tested on ia64-suse-linux and installed as obvious.
>
> Please don't add the TLS symbols in there, they aren't included
> in any of the linux baselines
Actually, there are some:
libstdc++-v3/config/abi/po
On Thu, Apr 10, 2014 at 09:52:35AM +0200, Andreas Schwab wrote:
> Tested on ia64-suse-linux and installed as obvious.
Please don't add the TLS symbols in there, they aren't included
in any of the linux baselines so that there aren't failures in
--disable-tls configurations or when using too old bi
