From: Richard Earnshaw <rearnsha@arm.com>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ARM] TLS Descriptor support
Date: Tue, 07 Jun 2011 13:08:00 -0000 [thread overview]
Message-ID: <4DEE229F.1020007@arm.com> (raw)
In-Reply-To: <4DEDC0FB.1060605@codesourcery.com>
On 06/07/11 07:11, Nathan Sidwell wrote:
> On 06/06/11 17:27, Richard Earnshaw wrote:
>
>> Eh? This is backwards. There is blx <reg>, but no bl <reg>. If the assembler
>> gets confused with 'bl r0' then it needs to be fixed urgently.
>
> Are you requiring the assembler be fixed before this patch can be committed
> (without the '+'?)
>
> nathan
>
Yes, the assembler output here should be "bl\\t%c0(tlsdesc)" for all
variants.
I'd also much prefer that the named variant be GNU and GNU2, as they are
for x86. It's much less confusing to users that way (the fact that the
first (GNU) variant is documented in the ARM ABI specification is simply
down to a lack of external documentation to refer to, but the underlying
model is the same as that used elsewere for the first GNU version).
R.
next prev parent reply other threads:[~2011-06-07 13:08 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
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 [this message]
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=4DEE229F.1020007@arm.com \
--to=rearnsha@arm.com \
--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).