On Mon, Jul 27, 2020 at 8:05 AM Andrea Righi <[email protected]> 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
On Thu, Jul 30, 2020 at 10:11:52AM -0500, Justin Forbes wrote:
> On Mon, Jul 27, 2020 at 8:05 AM Andrea Righi <[email protected]> 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