linux-kernel - Re: [PATCH] mach-bcm SMC: address clang inline asm incompatibility

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <53B2A7D4.4020007@linaro.org>
Date:	Tue, 01 Jul 2014 07:21:40 -0500
From:	Alex Elder <elder@...aro.org>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
CC:	bcm@...thebug.org, mporter@...aro.org,
	bcm-kernel-feedback-list@...adcom.com,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] mach-bcm SMC: address clang inline asm incompatibility

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/