From: Nathan Sidwell <nathan@codesourcery.com>
To: Ramana Radhakrishnan <ramana.radhakrishnan@linaro.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ARM] TLS Descriptor support
Date: Tue, 31 May 2011 13:03:00 -0000 [thread overview]
Message-ID: <4DE4BCE2.8050501@codesourcery.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2011-05-31 10:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 11:23 Nathan Sidwell
2011-05-10 13:14 ` Joseph S. Myers
2011-05-11 15:43 ` Nathan Sidwell
2011-05-26 9:32 ` Nathan Sidwell
2011-05-27 4:43 ` Ramana Radhakrishnan
2011-05-31 13:03 ` Nathan Sidwell [this message]
2011-06-03 22:50 ` Ramana Radhakrishnan
2011-06-06 9:50 ` Nathan Sidwell
2011-06-06 9:54 ` Ramana Radhakrishnan
2011-06-06 9:56 ` Nathan Sidwell
2011-06-06 16:10 ` Ramana Radhakrishnan
2011-06-06 16:27 ` Richard Earnshaw
2011-06-07 6:11 ` Nathan Sidwell
2011-06-07 13:08 ` Richard Earnshaw
2011-06-21 8:42 ` Nathan Sidwell
2011-06-21 18:03 ` Ramana Radhakrishnan
2011-06-22 17:52 ` Nathan Sidwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DE4BCE2.8050501@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramana.radhakrishnan@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).