Announce: rmk's nightly builder gets ARM64 support

[will.deacon@arm.com (Will Deacon)]

[adding Ard]

On Thu, Feb 19, 2015 at 06:34:44PM +0000, Russell King - ARM Linux wrote:
> On Thu, Feb 19, 2015 at 05:12:20PM +0000, Russell King - ARM Linux wrote:
> > Today, I have added ARM64 support to my automated nightly kernel builder.
> > Initially, this will result in ARM64 builds being tested with allnoconfig
> > and defconfig, and I shall add allmodconfig and allyesconfig to this in
> > the coming days.
> > 
> > Once that is done and stable, I will investigate adding an ARM Juno
> > platform to my boot farm so we can run the results of the builder.
> > 
> > Other recent changes have been a disk upgrade, so the builder now has
> > plenty of disk space to run the allmodconfig and allyesconfig, which
> > used to fail (or be skipped) when the disk space was low.
> > 
> > I've also added a new ARM target for building the defconfig without a
> > seed.
> > 
> > As ever, all results are in the usual place, at:
> > 
> > http://www.arm.linux.org.uk/developer/build/
> 
> It seems that there's either something wrong with the kernel, or
> there's a problem with binutils.
> 
> /tmp/cc1B9ysz.s:99: Error: selected processor does not support `aese v0.16b,v1.16b'
> /tmp/cc1B9ysz.s:207: Error: selected processor does not support `aesimc v1.16b,v0.16b'
> /tmp/cc1B9ysz.s:255: Error: selected processor does not support `aese v0.16b,v1.16b'
> /tmp/cc1B9ysz.s:389: Error: selected processor does not support `aesd v0.16b,v2.16b'
> /tmp/cc1B9ysz.s:389: Error: selected processor does not support `aesimc v0.16b,v0.16b'
> /tmp/cc1B9ysz.s:389: Error: selected processor does not support `aesd v0.16b,v3.16b'
> /tmp/cc1B9ysz.s:389: Error: selected processor does not support `aesimc v0.16b,v0.16b'
> /tmp/cc1B9ysz.s:389: Error: selected processor does not support `aesd v0.16b,v1.16b'
> /tmp/cc1B9ysz.s:389: Error: selected processor does not support `aesimc v0.16b,v0.16b'
> /tmp/cc1B9ysz.s:389: Error: selected processor does not support `aesd v0.16b,v2.16b'
> /tmp/cc1B9ysz.s:455: Error: selected processor does not support `aese v0.16b,v2.16b'
> /tmp/cc1B9ysz.s:455: Error: selected processor does not support `aesmc v0.16b,v0.16b'
> /tmp/cc1B9ysz.s:455: Error: selected processor does not support `aese v0.16b,v3.16b'
> /tmp/cc1B9ysz.s:455: Error: selected processor does not support `aesmc v0.16b,v0.16b'
> /tmp/cc1B9ysz.s:455: Error: selected processor does not support `aese v0.16b,v1.16b'
> /tmp/cc1B9ysz.s:455: Error: selected processor does not support `aesmc v0.16b,v0.16b'
> /tmp/cc1B9ysz.s:455: Error: selected processor does not support `aese v0.16b,v2.16b'
> make[2]: *** [arch/arm64/crypto/aes-ce-cipher.o] Error 1
> 
> I've tried both the mainline git version, and the sourceware.org
> binutils-gdb.git version, both result in the same errors.

It sounds like GCC isn't propagating the march flags down to the assembler,
since we take care in arch/arm64/crypto/Makefile to pass the '+crypto'
option for these files.

It's weird that nobody else is reporting this. I'm not saying that we
shouldn't look at fixing it, but I'd like to understand why you're hitting
this and I'm not as it could reveal a gap in our build testing.

Will