This is the mail archive of the
mailing list for the GCC project.
Re: Failure to dlopen libgomp due to static TLS data
- From: Rich Felker <dalias at libc dot org>
- To: Jakub Jelinek <jakub at redhat dot com>
- 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 11:16:17 -0500
- 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> <20150212161145 dot GD1746 at tucnak dot redhat dot com>
On Thu, Feb 12, 2015 at 05:11:45PM +0100, Jakub Jelinek wrote:
> 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.
Seems very unlikely. If storage is allocated in static TLS, TLSDESC is
almost indistinguishable from IE in performance, even when you run
artificial benchmarks that do nothing but hammer TLS access. When it
gets allocated in dynamic TLS, it's somewhat slower, but still
unlikely to matter for most usage IMO. Do you have actual numbers
showing that TLSDESC is too slow for libgomp?