[Bug libc/16291] feature request: provide simpler ways to compute stack and tls boundaries

["bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16291

--- Comment #20 from Rich Felker <bugdal at aerifal dot cx> ---
I'm not convinced that __libc_on_dynamic_tls_create and
__libc_on_dynamic_tls_destroy are a good API. Assuming they're called when the
thread obtains new TLS storage, the implementations of these functions would
need to be both thread-safe and AS-safe. This requirement would at least need
to be documented.

A cleaner API alternative might be to provide an iterator for TLS memory ranges
in the current thread, similar to how dl_iterate_phdr works for loaded DSOs.
This would avoid placing complex safety requirements on the component using the
API and would avoid having global state. (Interposing symbols over top of
libc-internal symbols is a NASTY hidden global state, since it admits only one
client to the API.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.