Florian Weimer via Gcc writes:
> [...]
> On other architectures with support for GNU2 TLS descriptors, those are
> used by default.
>
It looks like arm32 defaults to gnu, not gnu2. andrew mentioned fdpic
will be an issue there but maybe we could carve that out.
> Should we flip the default to
On Wed, Dec 13, 2023 at 1:08 PM Andrew Pinski wrote:
>
> On Wed, Dec 13, 2023 at 6:19 AM Florian Weimer via Gcc
> wrote:
> >
> > I feel like I have asked this before. Currently, GCC uses calls to
> > __tls_get_addr to obtain the address of global-dynamic TLS variables.
> > On other architecture
On Wed, Dec 13, 2023 at 6:19 AM Florian Weimer via Gcc wrote:
>
> I feel like I have asked this before. Currently, GCC uses calls to
> __tls_get_addr to obtain the address of global-dynamic TLS variables.
> On other architectures with support for GNU2 TLS descriptors, those are
> used by default.
Florian Weimer via Gcc writes:
> I feel like I have asked this before. Currently, GCC uses calls to
> __tls_get_addr to obtain the address of global-dynamic TLS variables.
> On other architectures with support for GNU2 TLS descriptors, those are
> used by default.
>
> Should we flip the defaul
On Wed, Dec 13, 2023 at 6:19 AM Florian Weimer via Gcc wrote:
>
> I feel like I have asked this before. Currently, GCC uses calls to
> __tls_get_addr to obtain the address of global-dynamic TLS variables.
> On other architectures with support for GNU2 TLS descriptors, those are
> used by default.
I feel like I have asked this before. Currently, GCC uses calls to
__tls_get_addr to obtain the address of global-dynamic TLS variables.
On other architectures with support for GNU2 TLS descriptors, those are
used by default.
Should we flip the default to GNU2 descriptors? Support has been
avail
