This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: TLS configure check question (why assembly?)
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Steve Ellcey <sellcey at mips dot com>
- Cc: <libc-alpha at sourceware dot org>, "Maciej W. Rozycki" <macro at codesourcery dot com>
- Date: Tue, 10 Jul 2012 16:34:50 +0000
- Subject: Re: TLS configure check question (why assembly?)
- References: <661716fd-78f0-4774-ad53-4b2170727aa5@EXCHHUB01.MIPS.com>
On Tue, 10 Jul 2012, Steve Ellcey wrote:
> I have noticed that most (all?) of the architecture specific configure
> scripts (sysdeps/*/configure.in, ports/sysdeps/*/configure.in) have
> a chunk of assembly code in them to verify that the assembler and linker
> support thread local storage.
I think those tests could now be considered obsolete and could be removed
- the requirement for binutils version 2.20 or later means TLS support can
be assumed to be present.
> The reason I ask is that the mips assembly language code that checks
> for TLS does not compile if you build glibc with the -mips16 flag and
> I wanted to understand why it is in assembly as opposed to C.
Mentor's MIPS16 glibc patches include a ".set nomips16" addition to this
test. I don't know when Maciej will be contributing those changes.
--
Joseph S. Myers
joseph@codesourcery.com