From: Sam James <sam@gentoo.org>
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 19:58:43 +0000 [thread overview]
Message-ID: <87fs05c1qz.fsf@gentoo.org> (raw)
In-Reply-To: <871qbqp4of.fsf@oldenburg.str.redhat.com>
Florian Weimer via Gcc <gcc@gcc.gnu.org> 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 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.
>
I was planning on bringing this up but I was worried there was some
reason we hadn't done it given it's been so long. Thank you!
next prev parent reply other threads:[~2023-12-13 19:59 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 [this message]
2023-12-13 21:08 ` Andrew Pinski
2023-12-14 5:47 ` Andrew Pinski
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=87fs05c1qz.fsf@gentoo.org \
--to=sam@gentoo.org \
--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).