From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: TLS support for (almost) all supported archs
Date: Mon, 15 Oct 2012 19:07:23 -0400 [thread overview]
Message-ID: <20121015230723.GA787@brightrain.aerifal.cx> (raw)
As of the latest commit, thread-local storage is working for i386,
x86_64, ARM, MIPS, and is theoretically partially working for
microblaze (I have no test platform for it yet, and some of the
dynamic linker relocation stuff is missing for some usage cases).
This brings us a lot closer to the next release, in which TLS and
microblaze support (hopefully for both of them together!) will be the
highlights. Most testing so far has been dumb test-cases, so if
anybody has real-world apps that make heavy use of TLS that would be
good trials to see if TLS is "really working", please try and let me
know how it goes.
One further change I've been considering and might try to get in
before this release is C++ ABI compatibility. It looks like not many
types would need changing to make musl name-mangling-ABI-compatible
with C++ apps linked to glibc, but I haven't looked into the issues in
detail yet. If you're looking for something to help out with, figuring
out how extensive the changes would need to be would be a very helpful
task (and would help determine if it's feasible at all, as well as if
it's feasible to target in the next release).
Rich
reply other threads:[~2012-10-15 23:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121015230723.GA787@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).