about summary refs log tree commit diff
path: root/arch/microblaze/bits
diff options
context:
space:
mode:
authorRich Felker <dalias@aerifal.cx>2012-10-15 18:51:53 -0400
committerRich Felker <dalias@aerifal.cx>2012-10-15 18:51:53 -0400
commit9ec4283b28cf676292fd5c6f681bef1e90e30c18 (patch)
tree2897be56744c39158a3e53adfc4e3569b3f8547d /arch/microblaze/bits
parentd5304147b983f309ed0c9050e3b8b6f2c9f87f43 (diff)
downloadmusl-9ec4283b28cf676292fd5c6f681bef1e90e30c18.tar.gz
musl-9ec4283b28cf676292fd5c6f681bef1e90e30c18.tar.xz
musl-9ec4283b28cf676292fd5c6f681bef1e90e30c18.zip
add support for TLS variant I, presently needed for arm and mips
despite documentation that makes it sound a lot different, the only
ABI-constraint difference between TLS variants II and I seems to be
that variant II stores the initial TLS segment immediately below the
thread pointer (i.e. the thread pointer points to the end of it) and
variant I stores the initial TLS segment above the thread pointer,
requiring the thread descriptor to be stored below. the actual value
stored in the thread pointer register also tends to have per-arch
random offsets applied to it for silly micro-optimization purposes.

with these changes applied, TLS should be basically working on all
supported archs except microblaze. I'm still working on getting the
necessary information and a working toolchain that can build TLS
binaries for microblaze, but in theory, static-linked programs with
TLS and dynamic-linked programs where only the main executable uses
TLS should already work on microblaze.

alignment constraints have not yet been heavily tested, so it's
possible that this code does not always align TLS segments correctly
on archs that need TLS variant I.
Diffstat (limited to 'arch/microblaze/bits')
0 files changed, 0 insertions, 0 deletions