diff options
author | Rich Felker <dalias@aerifal.cx> | 2019-02-17 23:22:27 -0500 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2019-02-18 21:01:16 -0500 |
commit | 9d44b6460ab603487dab4d916342d9ba4467e6b9 (patch) | |
tree | c7aa27a062fe7847972b204ced082217b5e8b0ad /src/multibyte/btowc.c | |
parent | 805288929fdf511b4044cf07c59e02e2eaa9c546 (diff) | |
download | musl-9d44b6460ab603487dab4d916342d9ba4467e6b9.tar.gz musl-9d44b6460ab603487dab4d916342d9ba4467e6b9.tar.bz2 musl-9d44b6460ab603487dab4d916342d9ba4467e6b9.tar.xz musl-9d44b6460ab603487dab4d916342d9ba4467e6b9.zip |
install dynamic tls synchronously at dlopen, streamline access
previously, dynamic loading of new libraries with thread-local storage
allocated the storage needed for all existing threads at load-time,
precluding late failure that can't be handled, but left installation
in existing threads to take place lazily on first access. this imposed
an additional memory access and branch on every dynamic tls access,
and imposed a requirement, which was not actually met, that the
dynamic tlsdesc asm functions preserve all call-clobbered registers
before calling C code to to install new dynamic tls on first access.
the x86[_64] versions of this code wrongly omitted saving and
restoring of fpu/vector registers, assuming the compiler would not
generate anything using them in the called C code. the arm and aarch64
versions saved known existing registers, but failed to be future-proof
against expansion of the register file.
now that we track live threads in a list, it's possible to install the
new dynamic tls for each thread at dlopen time. for the most part,
synchronization is not needed, because if a thread has not
synchronized with completion of the dlopen, there is no way it can
meaningfully request access to a slot past the end of the old dtv,
which remains valid for accessing slots which already existed.
however, it is necessary to ensure that, if a thread sees its new dtv
pointer, it sees correct pointers in each of the slots that existed
prior to the dlopen. my understanding is that, on most real-world
coherency architectures including all the ones we presently support, a
built-in consume order guarantees this; however, don't rely on that.
instead, the SYS_membarrier syscall is used to ensure that all threads
see the stores to the slots of their new dtv prior to the installation
of the new dtv. if it is not supported, the same is implemented in
userspace via signals, using the same mechanism as __synccall.
the __tls_get_addr function, variants, and dynamic tlsdesc asm
functions are all updated to remove the fallback paths for claiming
new dynamic tls, and are now all branch-free.
Diffstat (limited to 'src/multibyte/btowc.c')
0 files changed, 0 insertions, 0 deletions