PATCH: Check TLS for libgcc

[Mike Stump]

On Jun 20, 2007, at 8:44 AM, H. J. Lu wrote:
> On Wed, Jun 20, 2007 at 10:57:42AM -0400, Daniel Jacobowitz wrote:
>> If I understand correctly, there will not be any major compatibility
>> problems when this changes - code will need to be recompiled to get
>> the rounding modes right, but existing binaries will continue to work
>
> Yes.
>
>> as well as they did before.  Right?  Then hidden symbols in libgcc.a
>> sounds like a good choice to me.
>
> They can't be hidden. Otherwise, we may have 2 copies of them, one in
> executable and one in DSO.

Hold on a second...

TLS is subject to an ABI change when going from emulated TLS to real  
TLS, right?

You want to export them (tls variables) from a libgcc shlib?

We want libgcc to be very abi stable.

How do we later add real TLS support to a platform (darwin) that  
doesn't have it now?

I'll object to anything exported from libgcc shlib that isn't designed  
to be abi stable?!