From: elder@linaro.org (Alex Elder)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] bcm: address clang inline asm incompatibility
Date: Wed, 28 Jan 2015 11:08:33 -0600 [thread overview]
Message-ID: <54C91791.9030508@linaro.org> (raw)
In-Reply-To: <CAKv+Gu8CrMqwqBOF8rYa3RP1=gfCthwP=1k9kQ73v6+Sxwah4A@mail.gmail.com>
On 01/28/2015 10:17 AM, Ard Biesheuvel wrote:
> On 28 January 2015 at 14:11, Alex Elder <elder@linaro.org> wrote:
>> On 01/28/2015 05:15 AM, Ard Biesheuvel wrote:
>>> On 28 January 2015 at 05:18, Behan Webster <behanw@converseincode.com> wrote:
>>>> From: Alex Elder <elder@linaro.org>
>>>>
>>>> My GCC-based build environment likes to call register r12 by the
>>>> name "ip" in inline asm. Behan Webster informed me that his Clang-
>>>> based build environment likes "r12" instead.
>>>>
>>>> Try to make them both happy.
>>>>
>>>> Signed-off-by: Alex Elder <elder@linaro.org>
>>>> Signed-off-by: Behan Webster <behanw@converseincode.com>
>>>> ---
>>>> arch/arm/mach-bcm/bcm_kona_smc.c | 9 +++++++--
>>>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/arch/arm/mach-bcm/bcm_kona_smc.c b/arch/arm/mach-bcm/bcm_kona_smc.c
>>>> index a55a7ec..3937bd5 100644
>>>> --- a/arch/arm/mach-bcm/bcm_kona_smc.c
>>>> +++ b/arch/arm/mach-bcm/bcm_kona_smc.c
>>>> @@ -106,9 +106,14 @@ int __init bcm_kona_smc_init(void)
>>>> * request result appropriately. This result value is found in r0
>>>> * when the "smc" request completes.
>>>> */
>>>> +#ifdef __clang__
>>>> +#define R12 "r12"
>>>> +#else /* !__clang__ */
>>>> +#define R12 "ip" /* gcc calls r12 "ip" */
>>>> +#endif /* !__clang__ */
>>>
>>> Why not just use r12 for both?
>>
>> Yes, that would have been an obvious fix. But the
>> assembler (in the GCC environment) doesn't accept that.
>>
>
> Mine has no problems with it at all
>
> $ echo 'mov r12, #0' | arm-linux-gnueabihf-gcc -c -x assembler-with-cpp -
>
> and grepping for r12 under arch/arm suggests the same
The use of "r12" is fine. But it's not just the assembler,
I believe it also involves gcc.
The problem is with the use of the __asmeq(x, y) macro.
If I assign the "ip" variable with "r12":
register u32 ip asm("r12"); /* Also called ip */
Then that's fine. However, this line then causes an error:
__asmeq("%0", "r12")
Apparently gcc uses register "ip" when it sees asm("r12"). So
attempting to verify the desired register got used with __asmeq()
causes a string mismatch--"ip" is not equal to "r12".
So I could use:
register u32 ip asm("r12"); /* Also called ip */
...
__asmeq("%0", "ip")
And that will build. But it's a little non-intuitive, and
I suspect that clang might (rightfully) have a failure in
this __asmeq() call.
-Alex
next prev parent reply other threads:[~2015-01-28 17:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 5:18 [PATCH] bcm: address clang inline asm incompatibility Behan Webster
2015-01-28 11:15 ` Ard Biesheuvel
2015-01-28 14:11 ` Alex Elder
2015-01-28 16:17 ` Ard Biesheuvel
2015-01-28 17:08 ` Alex Elder [this message]
2015-01-28 17:20 ` Ard Biesheuvel
2015-01-28 19:17 ` Ard Biesheuvel
2015-01-28 19:27 ` Alex Elder
2015-01-28 19:38 ` Ard Biesheuvel
2015-01-28 20:11 ` Ard Biesheuvel
2015-01-28 20:15 ` Alex Elder
2015-01-28 21:18 ` Behan Webster
2015-01-28 21:07 ` Behan Webster
2015-01-28 19:30 ` Behan Webster
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=54C91791.9030508@linaro.org \
--to=elder@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).