This is the mail archive of the
mailing list for the glibc project.
Re: Failure to dlopen libgomp due to static TLS data
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Rich Felker <dalias at libc dot org>
- Cc: Ulrich Weigand <uweigand at de dot ibm dot com>, libc-alpha at sourceware dot org, gcc at gcc dot gnu dot org, rth at redhat dot com
- Date: Thu, 12 Feb 2015 17:11:45 +0100
- Subject: Re: Failure to dlopen libgomp due to static TLS data
- Authentication-results: sourceware.org; auth=none
- References: <201502121519 dot t1CFJMAe018776 at d03av02 dot boulder dot ibm dot com> <20150212160959 dot GS23507 at brightrain dot aerifal dot cx>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Feb 12, 2015 at 11:09:59AM -0500, Rich Felker wrote:
> On Thu, Feb 12, 2015 at 04:18:57PM +0100, Ulrich Weigand wrote:
> > Hello,
> > we're running into a problem related to use of initial-exec access to
> > TLS variables in dynamically-loaded libraries. Now, in general, this
> > is actually not supported. However, there seems to an "inofficial"
> > extension that allows selected system libraries to use small amounts
> > of static TLS space to allow critical variables to be defined to use
> > the initial-exec model even in dynamically-loaded libraries.
> This usage is supposed to be deprecated. Why isn't libgomp using
> TLSDESC/gnu2 model?
Because it is significantly slower.