On Wed, Jul 5, 2017 at 9:27 AM, Florian Weimer <fwei...@redhat.com> wrote:
> On 07/05/2017 06:21 PM, H.J. Lu wrote:
>> On Wed, Jul 5, 2017 at 9:18 AM, Florian Weimer <fwei...@redhat.com> wrote:
>>> On 07/05/2017 06:17 PM, H.J. Lu wrote:
>>>> On Wed, Jul 5, 2017 at 9:09 AM, Florian Weimer <fwei...@redhat.com> wrote:
>>>>> On 07/05/2017 05:38 PM, H.J. Lu wrote:
>>>>>> We are considering to add an alternative interface, ___tls_get_addr, to
>>>>>> glibc, which doesn't realign stack.  Compilers, which properly align 
>>>>>> stack
>>>>>> for TLS, call generate call to ___tls_get_addr, instead of 
>>>>>> __tls_get_addr,
>>>>>> if ___tls_get_addr is available.
>>>>>
>>>>> Why can't we add a new symbol version instead?  Those who recompile or
>>>>> relink their applications would have to use fixed compilers.
>>>>>
>>>>
>>>> When GCC 4.8 is used to compile packages under the new glibc, the new
>>>> version of ___tls_get_addr will be used.  But the alignment will be wrong.
>>>
>>> GCC 4.8 is out of support.  Do not use it, or use it along with a
>>> matching glibc.
>>
>> We do support old GCCs to be used with the new glibc, just not to support
>> them to build glibc.
>
> There is no promise that we will work around compiler bugs in old GCCs,
> though.

We are supporting older GCCs as much as we can.


-- 
H.J.

Reply via email to