All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"David S. Miller" <davem@davemloft.net>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Felipe Balbi <balbi@kernel.org>
Subject: Re: [build break] aegis128-neon-inner.c fails to build on v5.9-rc1
Date: Fri, 21 Aug 2020 12:52:38 +0200	[thread overview]
Message-ID: <CAMj1kXGwAjrhgFt7ayO=S0UMdDu2KSqv=4R22poGRj_HDhQqRw@mail.gmail.com> (raw)
In-Reply-To: <20200821035454.GA25551@gondor.apana.org.au>

On Fri, 21 Aug 2020 at 05:55, Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> On Mon, Aug 17, 2020 at 03:03:11PM +0300, Felipe Balbi wrote:
> >
> > Hi,
> >
> > I'm not sure if there's already a patch for this, but I notices arm64
> > allmodconfig fails to build with GCC 10.2 as shown below:
> >
> > crypto/aegis128-neon-inner.c: In function 'crypto_aegis128_init_neon':
> > crypto/aegis128-neon-inner.c:151:3: error: incompatible types when initializing type 'unsigned char' using type 'uint8x16_t'
> >   151 |   k ^ vld1q_u8(const0),
> >       |   ^
> > crypto/aegis128-neon-inner.c:152:3: error: incompatible types when initializing type 'unsigned char' using type 'uint8x16_t'
> >   152 |   k ^ vld1q_u8(const1),
> >       |   ^
> > crypto/aegis128-neon-inner.c:147:29: warning: missing braces around initializer [-Wmissing-braces]
> >   147 |  struct aegis128_state st = {{
> >       |                             ^
> > ......
> >   151 |   k ^ vld1q_u8(const0),
> >       |   {
> >   152 |   k ^ vld1q_u8(const1),
> >   153 |  }};
> >       |  }
> >
> > Confirmation of GCC version follows:
> >
> > $ aarch64-linux-gnu-gcc --version
> > aarch64-linux-gnu-gcc (GCC) 10.2.0
> > Copyright (C) 2020 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions.  There is NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> Ard, can you please take a look at this?
>

This is a known regression in GCC [0] that has already been fixed. GCC
10.3 should work fine.


[0] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96377

      reply	other threads:[~2020-08-21 10:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ft8l1nuo.fsf@kernel.org>
2020-08-21  3:54 ` [build break] aegis128-neon-inner.c fails to build on v5.9-rc1 Herbert Xu
2020-08-21 10:52   ` Ard Biesheuvel [this message]

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='CAMj1kXGwAjrhgFt7ayO=S0UMdDu2KSqv=4R22poGRj_HDhQqRw@mail.gmail.com' \
    --to=ardb@kernel.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=balbi@kernel.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.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.