mailing list of musl libc
 help / color / mirror / code / Atom feed
From: " ." <yedexi1996@qq.com>
To: musl <musl@lists.openwall.com>
Subject: [musl] Question about the TLS
Date: Tue, 17 Dec 2024 15:11:06 +0800	[thread overview]
Message-ID: <tencent_51AD597182952DD4F9D2EBA5CE20E587AE0A@qq.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 416 bytes --]

Hi
I have one question in TLS.
I intend to incorporate a Thread-Local Storage (TLS) variable into the musl library.&nbsp; However, the musl library does not currently support the&nbsp;
handling of TLS variables within the ldso library.&nbsp; Could you please advise if there are any potential risks or issues associated with adding TLS
&nbsp;variables and the corresponding processing logic?
Best 
ye

&nbsp;

[-- Attachment #2: Type: text/html, Size: 568 bytes --]

             reply	other threads:[~2024-12-17 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  7:11  . [this message]
2024-12-17 16:25 ` Markus Wichmann
2024-12-21  6:22   ` Rich Felker

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=tencent_51AD597182952DD4F9D2EBA5CE20E587AE0A@qq.com \
    --to=yedexi1996@qq.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).