From: elder@linaro.org (Alex Elder)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mach-bcm SMC: address clang inline asm incompatibility
Date: Tue, 01 Jul 2014 07:21:40 -0500 [thread overview]
Message-ID: <53B2A7D4.4020007@linaro.org> (raw)
In-Reply-To: <20140701121544.GK32514@n2100.arm.linux.org.uk>
On 07/01/2014 07:15 AM, Russell King - ARM Linux wrote:
> On Tue, Jul 01, 2014 at 07:05:39AM -0500, Alex Elder wrote:
>> 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.
>
> Two objections, one of which is an acceptable outcome:
> 1. Why can't clang just learn these alternative names?
I suggested that. I don't know where to send that suggestion
though.
> 2. Why can't we just use "r12" here?
I don't recall the details, but when I wrote the code originally
that way it gave me errors. It's why I had the "Also called r12"
comment next to the symbol declaration.
I agree, I'd rather have either one of those than this #ifdef
workaround. I was supplying this as a potentially quicker fix
for the problem Behan was hitting.
-Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alex Elder <elder@linaro.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: bcm@fixthebug.org, mporter@linaro.org,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mach-bcm SMC: address clang inline asm incompatibility
Date: Tue, 01 Jul 2014 07:21:40 -0500 [thread overview]
Message-ID: <53B2A7D4.4020007@linaro.org> (raw)
In-Reply-To: <20140701121544.GK32514@n2100.arm.linux.org.uk>
On 07/01/2014 07:15 AM, Russell King - ARM Linux wrote:
> On Tue, Jul 01, 2014 at 07:05:39AM -0500, Alex Elder wrote:
>> 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.
>
> Two objections, one of which is an acceptable outcome:
> 1. Why can't clang just learn these alternative names?
I suggested that. I don't know where to send that suggestion
though.
> 2. Why can't we just use "r12" here?
I don't recall the details, but when I wrote the code originally
that way it gave me errors. It's why I had the "Also called r12"
comment next to the symbol declaration.
I agree, I'd rather have either one of those than this #ifdef
workaround. I was supplying this as a potentially quicker fix
for the problem Behan was hitting.
-Alex
next prev parent reply other threads:[~2014-07-01 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 12:05 [PATCH] mach-bcm SMC: address clang inline asm incompatibility Alex Elder
2014-07-01 12:05 ` Alex Elder
2014-07-01 12:15 ` Russell King - ARM Linux
2014-07-01 12:15 ` Russell King - ARM Linux
2014-07-01 12:21 ` Alex Elder [this message]
2014-07-01 12:21 ` Alex Elder
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=53B2A7D4.4020007@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.