* crypto: aegis128: error: incompatible types when initializing type 'unsigned char' using type 'uint8x16_t'
@ 2020-07-27 13:05 Andrea Righi
2020-07-30 15:11 ` Justin Forbes
0 siblings, 1 reply; 3+ messages in thread
From: Andrea Righi @ 2020-07-27 13:05 UTC (permalink / raw)
To: Herbert Xu, David S. Miller; +Cc: linux-crypto, linux-kernel
I'm experiencing this build error on arm64 after updating to gcc 10:
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),
| ^
Anybody knows if there's a fix for this already? Otherwise I'll take a look at it.
Thanks,
-Andrea
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: crypto: aegis128: error: incompatible types when initializing type 'unsigned char' using type 'uint8x16_t'
2020-07-27 13:05 crypto: aegis128: error: incompatible types when initializing type 'unsigned char' using type 'uint8x16_t' Andrea Righi
@ 2020-07-30 15:11 ` Justin Forbes
2020-07-30 15:21 ` Andrea Righi
0 siblings, 1 reply; 3+ messages in thread
From: Justin Forbes @ 2020-07-30 15:11 UTC (permalink / raw)
To: Andrea Righi; +Cc: Herbert Xu, David S. Miller, linux-crypto, LKML
On Mon, Jul 27, 2020 at 8:05 AM Andrea Righi <andrea.righi@canonical.com> wrote:
>
> I'm experiencing this build error on arm64 after updating to gcc 10:
>
> 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),
> | ^
>
> Anybody knows if there's a fix for this already? Otherwise I'll take a look at it.
I hit it and have been working with Jakub on the issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96377
Justin
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: crypto: aegis128: error: incompatible types when initializing type 'unsigned char' using type 'uint8x16_t'
2020-07-30 15:11 ` Justin Forbes
@ 2020-07-30 15:21 ` Andrea Righi
0 siblings, 0 replies; 3+ messages in thread
From: Andrea Righi @ 2020-07-30 15:21 UTC (permalink / raw)
To: Justin Forbes; +Cc: Herbert Xu, David S. Miller, linux-crypto, LKML
On Thu, Jul 30, 2020 at 10:11:52AM -0500, Justin Forbes wrote:
> On Mon, Jul 27, 2020 at 8:05 AM Andrea Righi <andrea.righi@canonical.com> wrote:
> >
> > I'm experiencing this build error on arm64 after updating to gcc 10:
> >
> > 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),
> > | ^
> >
> > Anybody knows if there's a fix for this already? Otherwise I'll take a look at it.
>
>
> I hit it and have been working with Jakub on the issue.
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96377
>
> Justin
Thanks, Justin! I'll keep an eye at this bug report.
-Andrea
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-07-30 15:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-27 13:05 crypto: aegis128: error: incompatible types when initializing type 'unsigned char' using type 'uint8x16_t' Andrea Righi
2020-07-30 15:11 ` Justin Forbes
2020-07-30 15:21 ` Andrea Righi
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).