public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Switching x86_64-linux-gnu to GNU2 TLS descriptors by default
Date: Wed, 13 Dec 2023 21:47:26 -0800	[thread overview]
Message-ID: <CA+=Sn1m6aokR9aGe3o8UAPkXuzui3sUcu0=XR=qmZ96gTnLcww@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1mnq-qS6V9MEdFQs8nLA9uTR8WfqgqKN3hX93JwfLvzJg@mail.gmail.com>

On Wed, Dec 13, 2023 at 1:08 PM Andrew Pinski <pinskia@gmail.com> wrote:
>
> On Wed, Dec 13, 2023 at 6:19 AM Florian Weimer via Gcc <gcc@gcc.gnu.org> 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.
> >
> > Should we flip the default to GNU2 descriptors?  Support has been
> > available in glibc for a long, long time.  Is there any other reason for
> > not doing this?  On the glibc side, the behavior regarding lazy
> > initialization and symbol binding does not change whether the old or new
> > interface is used.
>
> Just FYI, the last time this was asked was 6 years ago but maybe
> things has changed since:
> https://inbox.sourceware.org/gcc-patches/CAMe9rOp_68qpdLz25PoHa1ewB6pGQuVv_+H5bXGFhU05MH9+Vg@mail.gmail.com/

Oh I noticed that was a bug filed before that asking for testcases to
be added for it on x86_64 but it looks like it was not implemented:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48868

So it might even be broken.

Thanks,
Andrew


>
> Thanks,
> Andrew
>
> >
> > Thanks,
> > Florian
> >

  reply	other threads:[~2023-12-14  5:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 14:17 Florian Weimer
2023-12-13 17:53 ` H.J. Lu
2023-12-13 19:58 ` Sam James
2023-12-13 21:08 ` Andrew Pinski
2023-12-14  5:47   ` Andrew Pinski [this message]
2023-12-14  6:28 ` Sam James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+=Sn1m6aokR9aGe3o8UAPkXuzui3sUcu0=XR=qmZ96gTnLcww@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).