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 14:15:06 -0600 [thread overview]
Message-ID: <54C9434A.30000@linaro.org> (raw)
In-Reply-To: <CAKv+Gu8B7G3tNahkguDBjCOQih4_ywRtwaJz2D2b+vY1249-DA@mail.gmail.com>
On 01/28/2015 02:11 PM, Ard Biesheuvel wrote:
> Actually, if clang is guaranteed to emit the correct register name
> inside the inline asm for register asm variables used in input or
> output constraints, I think it makes sense to #define __asmeq as a nop
> if __clang__ is defined. (Note that __asmeq only exists to work around
> a specific GCC bug)
I agree completely. Behan, what do you think? -Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alex Elder <elder@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Behan Webster <behanw@converseincode.com>,
bcm@fixthebug.org, Florian Fainelli <f.fainelli@gmail.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Matt Porter <mporter@linaro.org>,
bcm-kernel-feedback-list@broadcom.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] bcm: address clang inline asm incompatibility
Date: Wed, 28 Jan 2015 14:15:06 -0600 [thread overview]
Message-ID: <54C9434A.30000@linaro.org> (raw)
In-Reply-To: <CAKv+Gu8B7G3tNahkguDBjCOQih4_ywRtwaJz2D2b+vY1249-DA@mail.gmail.com>
On 01/28/2015 02:11 PM, Ard Biesheuvel wrote:
> Actually, if clang is guaranteed to emit the correct register name
> inside the inline asm for register asm variables used in input or
> output constraints, I think it makes sense to #define __asmeq as a nop
> if __clang__ is defined. (Note that __asmeq only exists to work around
> a specific GCC bug)
I agree completely. Behan, what do you think? -Alex
next prev parent reply other threads:[~2015-01-28 20:15 UTC|newest]
Thread overview: 28+ 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 5:18 ` Behan Webster
2015-01-28 11:15 ` Ard Biesheuvel
2015-01-28 11:15 ` Ard Biesheuvel
2015-01-28 14:11 ` Alex Elder
2015-01-28 14:11 ` Alex Elder
2015-01-28 16:17 ` Ard Biesheuvel
2015-01-28 16:17 ` Ard Biesheuvel
2015-01-28 17:08 ` Alex Elder
2015-01-28 17:08 ` Alex Elder
2015-01-28 17:20 ` Ard Biesheuvel
2015-01-28 17:20 ` Ard Biesheuvel
2015-01-28 19:17 ` Ard Biesheuvel
2015-01-28 19:17 ` Ard Biesheuvel
2015-01-28 19:27 ` Alex Elder
2015-01-28 19:27 ` Alex Elder
2015-01-28 19:38 ` Ard Biesheuvel
2015-01-28 19:38 ` Ard Biesheuvel
2015-01-28 20:11 ` Ard Biesheuvel
2015-01-28 20:11 ` Ard Biesheuvel
2015-01-28 20:15 ` Alex Elder [this message]
2015-01-28 20:15 ` Alex Elder
2015-01-28 21:18 ` Behan Webster
2015-01-28 21:18 ` Behan Webster
2015-01-28 21:07 ` Behan Webster
2015-01-28 21:07 ` Behan Webster
2015-01-28 19:30 ` 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=54C9434A.30000@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.