There are a couple files in an ARM build which fail because of ARM Neon intrinsics: lib/raid6/recov_neon_inner.c and crypto/aegis128-neon-inner.c CHECK crypto/aegis128-neon-inner.c crypto/aegis128-neon-inner.c: note: in included file (through arch/arm64/include/asm/neon-intrinsics.h): /usr/lib/gcc-cross/aarch64-linux-gnu/12/include/arm_neon.h:40:9: warning: '__Int8x8_t' has implicit type /usr/lib/gcc-cross/aarch64-linux-gnu/12/include/arm_neon.h:40:20: error: Expected ; at end of declaration /usr/lib/gcc-cross/aarch64-linux-gnu/12/include/arm_neon.h:40:20: error: got int8x8_t /usr/lib/gcc-cross/aarch64-linux-gnu/12/include/arm_neon.h:41:21: error: Expected ; at end of declaration /usr/lib/gcc-cross/aarch64-linux-gnu/12/include/arm_neon.h:41:21: error: got int16x4_t /usr/lib/gcc-cross/aarch64-linux-gnu/12/include/arm_neon.h:42:21: error: Expected ; at end of declaration /usr/lib/gcc-cross/aarch64-linux-gnu/12/include/arm_neon.h:42:21: error: got int32x2_t /usr/lib/gcc-cross/aarch64-linux-gnu/12/include/arm_neon.h:43:21: error: Expected ; at end of declaration /usr/lib/gcc-cross/aarch64-linux-gnu/12/include/arm_neon.h:43:21: error: got int64x1_t /usr/lib/gcc-cross/aarch64-linux-gnu/12/include/arm_neon.h:44:23: error: Expected ; at end of declaration Neon intrinsics seem really complicated to handle, but maybe there is a hack around to just silence the warnings? regards, dan carpenter
