This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: TLS, 2015 edition
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: Stan Shebs <stanshebs at google dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Tue, 31 Mar 2015 11:26:02 +0100
- Subject: Re: TLS, 2015 edition
- Authentication-results: sourceware.org; auth=none
- References: <CA+5-Q5K7M3oJ-vvRP24GiCEHqnohWgqPkc7_6K9CLzc6a_MTcA at mail dot gmail dot com>
On 30/03/15 23:50, Stan Shebs wrote:
> Through a series of unfortunate events (starting with an infinite loop
> in an obscure Java test) I seem to have inherited the async-safe TLS
> problem.
>
i don't know about this bug, but i assume this is a lazy
binding issue
in that case linking with '-z now' should solve the problem
(..assuming glibc does the dynamic tls allocation at load
time then and at thread creation time)
> From what I can tell, there has not been much discussion following the
> patch reversion during 2.19's release process, aside from the proposal
> for a thread properties API:
>
> https://sourceware.org/ml/libc-alpha/2014-04/msg00313.html
>
> So where are things at now? From the extant discussion, I gather that
> there were some fundamental philosophical differences, and not even
> much meta-consensus on what consensus might look like. :-) Has
> anybody spent any time since then, thinking about this?
>
> If there are not any near-term prospects for agreement, I can fall
> back to fixing the immediate bugs in the Google-local patch, ugh.
>
> Stan
> stanshebs@google.com
>