From: Ramana Radhakrishnan <ramana.radhakrishnan@linaro.org>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ARM] TLS Descriptor support
Date: Fri, 03 Jun 2011 22:50:00 -0000 [thread overview]
Message-ID: <BANLkTim0BirFhU8snnHA_ShnXJrb-V48hA@mail.gmail.com> (raw)
In-Reply-To: <4DE4BCE2.8050501@codesourcery.com>
On 31 May 2011 11:03, Nathan Sidwell <nathan@codesourcery.com> wrote:
> 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.
I noticed this today - and maybe I don't quite understand it yet.
> /* The + is to avoid an assembly parse ambiguity with symbols that
> + look like register names, which is unsuccessfully recovered from. */
> + return TARGET_THUMB2 ? "blx\\t%c0(tlscall)" : "bl\\t+%c0(tlscall)";
How are things handled for Thumb1 in case someone builds a routine for
Thumb1 which uses tlsdesc ? I went and read the doc and didn't see any
difference between T1 and T2 in the specification . Would the linker
and everyone else do the right thing or should we have the blx
instruction for TARGET_THUMB and v5t . I have a feeling that I'm
missing something here .
cheers
Ramana
>
> nathan
>
> --
> Nathan Sidwell
>
>
next prev parent reply other threads:[~2011-06-03 22:50 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
2011-06-03 22:50 ` Ramana Radhakrishnan [this message]
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=BANLkTim0BirFhU8snnHA_ShnXJrb-V48hA@mail.gmail.com \
--to=ramana.radhakrishnan@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@codesourcery.com \
/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).