This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [ARM] TLS Descriptor support

From: Nathan Sidwell <nathan at codesourcery dot com>
To: Ramana Radhakrishnan <ramana dot radhakrishnan at linaro dot org>
Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Tue, 31 May 2011 11:03:14 +0100
Subject: Re: [ARM] TLS Descriptor support
References: <4DC8DFF6.4000600@codesourcery.com> <4DDEF499.9090206@linaro.org>

On 05/27/11 01:47, Ramana Radhakrishnan wrote:

Could you consider adding a check in the configury to test if a binutils version
of recent vintage is being used when --with-tls=gnu is in ?

I thought about that and it didn't seem worth it. We're not autodetecting whether to default to gnu-style tls and you'll find out soon enough if your binutils is too old.


Could you also use R0_REGNUM, R1_REGNUM instead of 0 and 1 in the "tlscall"
pattern ?

This patch has been tested for both default arm and default gnu tls
schemes using the gcc and glibc testsuites for an arm-linux-gnueabi target.
Presumably for v7-a and v5te and with this as default ? On hardware ?

Hm, I see our testing for fsf build uses qemu -- this patch has been tested on hardware in our releases. Just not this exact version of the patch.

nathan

--
Nathan Sidwell

References:
- [ARM] TLS Descriptor support
  - From: Nathan Sidwell
- Re: [ARM] TLS Descriptor support
  - From: Ramana Radhakrishnan

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]