Re: RFC: Add ___tls_get_addr

2017-07-06 Thread Rich Felker
On Thu, Jul 06, 2017 at 04:06:55AM -0700, H.J. Lu wrote: > > or there are cases when libraries built against > > one libc is used with another (e.g. musl can > > mostly use a libstdc++ compiled against glibc > > on x86_64) > > This happens every time when a new version of a function > is added to

Re: RFC: Add ___tls_get_addr

2017-07-06 Thread Carlos O'Donell
On 07/05/2017 12:02 PM, Rich Felker wrote: > Note that if you make the change and have gcc generate calls to the > new ___tls_get_addr symbol, it's going to be problematic for people > trying to link to older glibc versions that don't have it. This is a normal problem to have, and there are soluti

Re: RFC: Add ___tls_get_addr

2017-07-06 Thread H.J. Lu
On Thu, Jul 6, 2017 at 1:06 AM, Szabolcs Nagy wrote: > On 05/07/17 17:18, H.J. Lu wrote: >> On Wed, Jul 5, 2017 at 8:53 AM, Szabolcs Nagy wrote: >>> On 05/07/17 16:38, H.J. Lu wrote: On x86-64, __tls_get_addr has to realigns stack so that binaries compiled by GCCs older than GCC 4

Re: RFC: Add ___tls_get_addr

2017-07-06 Thread Szabolcs Nagy
On 05/07/17 17:18, H.J. Lu wrote: > On Wed, Jul 5, 2017 at 8:53 AM, Szabolcs Nagy wrote: >> On 05/07/17 16:38, H.J. Lu wrote: >>> On x86-64, __tls_get_addr has to realigns stack so that binaries compiled by >>> GCCs older than GCC 4.9.4: >>> >>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58066 >

Re: RFC: Add ___tls_get_addr

2017-07-05 Thread H.J. Lu
On Wed, Jul 5, 2017 at 9:27 AM, Florian Weimer wrote: > On 07/05/2017 06:21 PM, H.J. Lu wrote: >> On Wed, Jul 5, 2017 at 9:18 AM, Florian Weimer wrote: >>> On 07/05/2017 06:17 PM, H.J. Lu wrote: On Wed, Jul 5, 2017 at 9:09 AM, Florian Weimer wrote: > On 07/05/2017 05:38 PM, H.J. Lu wrot

Re: RFC: Add ___tls_get_addr

2017-07-05 Thread H.J. Lu
On Wed, Jul 5, 2017 at 8:51 AM, Carlos O'Donell wrote: > On 07/05/2017 11:38 AM, H.J. Lu wrote: >> On x86-64, __tls_get_addr has to realigns stack so that binaries compiled by >> GCCs older than GCC 4.9.4: >> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58066 >> >> continue to work even if vect

Re: RFC: Add ___tls_get_addr

2017-07-05 Thread H.J. Lu
On Wed, Jul 5, 2017 at 8:53 AM, Szabolcs Nagy wrote: > On 05/07/17 16:38, H.J. Lu wrote: >> On x86-64, __tls_get_addr has to realigns stack so that binaries compiled by >> GCCs older than GCC 4.9.4: >> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58066 >> >> continue to work even if vector inst

Re: RFC: Add ___tls_get_addr

2017-07-05 Thread Florian Weimer
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 availabl

Re: RFC: Add ___tls_get_addr

2017-07-05 Thread Rich Felker
On Wed, Jul 05, 2017 at 08:38:50AM -0700, H.J. Lu wrote: > On x86-64, __tls_get_addr has to realigns stack so that binaries compiled by > GCCs older than GCC 4.9.4: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58066 > > continue to work even if vector instructions are used by functions called

Re: RFC: Add ___tls_get_addr

2017-07-05 Thread Szabolcs Nagy
On 05/07/17 16:38, H.J. Lu wrote: > On x86-64, __tls_get_addr has to realigns stack so that binaries compiled by > GCCs older than GCC 4.9.4: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58066 > > continue to work even if vector instructions are used by functions called > from __tls_get_addr,

Re: RFC: Add ___tls_get_addr

2017-07-05 Thread Carlos O'Donell
On 07/05/2017 11:38 AM, H.J. Lu wrote: > On x86-64, __tls_get_addr has to realigns stack so that binaries compiled by > GCCs older than GCC 4.9.4: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58066 > > continue to work even if vector instructions are used by functions called > from __tls_get_