linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: linux-next: Tree for Jan 18
Date: Wed, 18 Jan 2017 15:44:59 -0500	[thread overview]
Message-ID: <CAP=VYLoirfK_wBSZuV_9YO_Cnm1SN=CsQ0zN5dZ6pMF4nU3D5g@mail.gmail.com> (raw)
In-Reply-To: <20170118163225.5776630e@canb.auug.org.au>

On Wed, Jan 18, 2017 at 12:32 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Changes since 20170117:
>
> The arm-soc tree gained a conflict against the arm tree.
>
> The amlogic tree gained a conflict against the arm-soc tree.
>
> Non-merge commits (relative to Linus' tree): 3676
>  4511 files changed, 139928 insertions(+), 85028 deletions(-)

Crypto now fails on arm allmodconfig:

arch/arm/crypto/Makefile:25: These ARMv8 Crypto Extensions modules
need binutils 2.23 or higher
arch/arm/crypto/Makefile:26:  aes-arm-ce.o sha1-arm-ce.o sha2-arm-ce.o
ghash-arm-ce.o crct10dif-arm-ce.o crc32-arm-ce.o
  AS [M]  arch/arm/crypto/aes-neonbs-core.o
  CC [M]  arch/arm/crypto/aes-neonbs-glue.o
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S: Assembler messages:
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1h[1],r10'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1h[0],r9'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1l[1],r8'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1l[0],r7'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
Error: bad type for scalar -- `vmov q2h[1],r10'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
Error: bad type for scalar -- `vmov q2h[0],r9'

[many more similar scalar errors deleted]

The 2.2.3 warning was there in the past, but it wasn't fatal.  I'm using
an older binutils 2.22 from the kernel.org crosstool stuff.

Seems sfr's builds get the same issue:

http://kisskb.ellerman.id.au/kisskb/buildresult/12910945/

A mindless "git bisect run" comes up with:

cc477bf645736739e69d31fdf715281ef0dd5f9b is the first bad commit
commit cc477bf645736739e69d31fdf715281ef0dd5f9b
Author: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Date:   Wed Jan 11 16:41:54 2017 +0000

    crypto: arm/aes - replace bit-sliced OpenSSL NEON code

Maybe binnutils 2.22 is finally too old?

Paul.
--

  reply	other threads:[~2017-01-18 20:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  5:32 linux-next: Tree for Jan 18 Stephen Rothwell
2017-01-18 20:44 ` Paul Gortmaker [this message]
2017-01-18 22:02   ` Ard Biesheuvel
2017-01-19 12:19   ` Ard Biesheuvel
  -- strict thread matches above, loose matches on Subject: below --
2024-01-18  3:31 Stephen Rothwell
2023-01-18  3:41 Stephen Rothwell
2022-01-18  2:59 Stephen Rothwell
2022-01-18  3:08 ` Stephen Rothwell
2021-01-18  6:48 Stephen Rothwell
2019-01-18  4:24 Stephen Rothwell
2018-01-18  7:16 Stephen Rothwell
2016-01-18  4:27 Stephen Rothwell
2013-01-18  4:37 Stephen Rothwell
2012-01-18  2:46 Stephen Rothwell

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='CAP=VYLoirfK_wBSZuV_9YO_Cnm1SN=CsQ0zN5dZ6pMF4nU3D5g@mail.gmail.com' \
    --to=paul.gortmaker@windriver.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).