David Benjamin 40c24d74de Don't use __ARMEL__/__ARMEB__ in aarch64 assembly ... GCC's __ARMEL__ and __ARMEB__ defines denote little- and big-endian arm, respectively. They are not defined on aarch64, which instead use __AARCH64EL__ and __AARCH64EB__. However, OpenSSL's assembly originally used the 32-bit defines on both platforms and even define __ARMEL__ and __ARMEB__ in arm_arch.h. This is less portable and can even interfere with other headers, which use __ARMEL__ to detect little-endian arm. Over time, the aarch64 assembly has switched to the correct defines, such as in 32bbb62ea6. This commit finishes the job: poly1305-armv8.pl needed a fix and the dual-arch armx.pl files get one more transform to convert from 32-bit to 64-bit. (There is an even more official endianness detector, __ARM_BIG_ENDIAN in the Arm C Language Extensions. But I've stuck with the GCC ones here as that would be a larger change.) Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Bernd Edlinger <bernd.edlinger@hotmail.de> (Merged from https://github.com/openssl/openssl/pull/17373)		2022-01-09 07:40:44 +01:00
..
asm	Don't use __ARMEL__/__ARMEB__ in aarch64 assembly	2022-01-09 07:40:44 +01:00
build.info	ppccap.c: Split out algorithm-specific functions	2021-06-25 08:49:45 +01:00
poly1305_base2_44.c	Update copyright year	2021-04-08 13:04:41 +01:00
poly1305_ieee754.c	Following the license change, modify the boilerplates in crypto/poly1305/	2018-12-06 15:13:16 +01:00
poly1305_ppc.c	ppccap.c: Split out algorithm-specific functions	2021-06-25 08:49:45 +01:00
poly1305.c	Update copyright year	2021-04-08 13:04:41 +01:00