From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9242 invoked by alias); 7 Jun 2011 13:08:17 -0000 Received: (qmail 9128 invoked by uid 22791); 7 Jun 2011 13:08:16 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,TW_BL X-Spam-Check-By: sourceware.org Received: from service87.mimecast.com (HELO service87.mimecast.com) (94.185.240.25) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Tue, 07 Jun 2011 13:07:50 +0000 Received: from cam-owa1.Emea.Arm.com (fw-tnat.cambridge.arm.com [217.140.96.21]) by service87.mimecast.com; Tue, 07 Jun 2011 14:07:46 +0100 Received: from [10.1.67.34] ([10.1.255.212]) by cam-owa1.Emea.Arm.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 7 Jun 2011 14:08:13 +0100 Message-ID: <4DEE229F.1020007@arm.com> Date: Tue, 07 Jun 2011 13:08:00 -0000 From: Richard Earnshaw User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: Nathan Sidwell CC: GCC Patches Subject: Re: [ARM] TLS Descriptor support References: <4DC8DFF6.4000600@codesourcery.com> <4DECFFE4.4060308@arm.com> <4DEDC0FB.1060605@codesourcery.com> In-Reply-To: <4DEDC0FB.1060605@codesourcery.com> X-MC-Unique: 111060714074607501 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2011-06/txt/msg00509.txt.bz2 On 06/07/11 07:11, Nathan Sidwell wrote: > On 06/06/11 17:27, Richard Earnshaw wrote: >=20 >> Eh? This is backwards. There is blx , but no bl . If the assem= bler >> gets confused with 'bl r0' then it needs to be fixed urgently. >=20 > Are you requiring the assembler be fixed before this patch can be committ= ed=20 > (without the '+'?) >=20 > nathan >=20 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.