From: Florian Weimer <fw@deneb.enyo.de>
To: Fengkai Sun via Libc-help <libc-help@sourceware.org>
Cc: Fengkai Sun <qcloud1014@gmail.com>
Subject: Re: CHECK_STATIC_TLS in R_X86_64_TPOFF64 type relocation
Date: Sun, 26 Dec 2021 16:48:26 +0100 [thread overview]
Message-ID: <87wnjrjrjp.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CAF6YOcMeKcekiiLj63ERTYXX_JdJSCSYmz48Qm4N-0B43nUneg@mail.gmail.com> (Fengkai Sun via Libc-help's message of "Sun, 26 Dec 2021 21:29:13 +0800")
* Fengkai Sun via Libc-help:
>> We are trying to perform a static TLS relocation in MAP, but it was
> dynamically loaded.
>
> To the best of my knowledge, I found that R_X86_64_TPOFF64 is for
> Initial-exec TLS model, which only appears in executables.
No, initial-exec in shared objects is fine (as long as static TLS
space is available).
Local-exec TLS in executables does not need relocations, and the link
editor typically relaxes initial-exec TLS reference in main programs
to local-exec TLS, leaving no of them trace (except for the PT_TLS
segment).
next prev parent reply other threads:[~2021-12-26 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 13:29 Fengkai Sun
2021-12-26 15:48 ` Florian Weimer [this message]
2021-12-27 3:05 ` Fengkai Sun
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=87wnjrjrjp.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-help@sourceware.org \
--cc=qcloud1014@gmail.com \
/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).