From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Long Subject: Re: glibc patch for TLS? Date: Mon, 25 Apr 2005 18:51:40 -0500 Message-ID: <95cbc48905042516517f772f9@mail.gmail.com> References: Reply-To: Michael Long Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: Nils Toedtmann , xen-devel List-Id: xen-devel@lists.xenproject.org That would be helpful, though the access still could be inside a library, which would be a be pain to track down in say, Mozilla or KDE. Still, it's better than nothing. -Michael On 4/25/05, Ian Pratt wrote: >=20 >=20 > > Nope, that's what I forgot. I recompiled the patched glibc > > with that flag and everything seems to be working fine. I > > can post the ebuild if people are interested. It's pretty > > straightforward, just adding the patch and making for the > > CFLAGS get set properly. > > > > I'm now compiling all my packages with > > -mno-tls-direct-seg-refs. Is this necessary/recommended? I > > know some ebuild strip out CFLAGS it's unsure of, so if it's > > necessary other packages may need to be modified. >=20 > Glibc really hammers the thread local storage stuff and hence > experiences rather more of a slow down rather than any applications > we've come across, but it would obviously be preferable to recompile > anything that uses tls. >=20 > One of the hard things is figuring out which applications actually make > use of the thread local attribute, and hence would actually benefit from > recompiling. >=20 > I guess we could modify the warning message to print out the name of the > process that did the -ve segment access... >=20 > Ian >