diff options
author | Adam Langley <agl@google.com> | 2015-01-10 02:44:37 +0300 |
---|---|---|
committer | Adam Langley <agl@google.com> | 2015-01-15 02:38:11 +0300 |
commit | 3e6526575ac2349a44a04a0bbc7acb917fab5a0b (patch) | |
tree | 51f4fbc4677ec256a8ff1f747df201f13ed50157 /crypto/cpu-intel.c | |
parent | bc44c089fbd87de0924130453058131ce30cd483 (diff) |
aarch64 support.
This is an initial cut at aarch64 support. I have only qemu to test it
however—hopefully hardware will be coming soon.
This also affects 32-bit ARM in that aarch64 chips can run 32-bit code
and we would like to be able to take advantage of the crypto operations
even in 32-bit mode. AES and GHASH should Just Work in this case: the
-armx.pl files can be built for either 32- or 64-bit mode based on the
flavour argument given to the Perl script.
SHA-1 and SHA-256 don't work like this however because they've never
support for multiple implementations, thus BoringSSL built for 32-bit
won't use the SHA instructions on an aarch64 chip.
No dedicated ChaCha20 or Poly1305 support yet.
Change-Id: Ib275bc4894a365c8ec7c42f4e91af6dba3bd686c
Reviewed-on: https://boringssl-review.googlesource.com/2801
Reviewed-by: Adam Langley <agl@google.com>
Diffstat (limited to 'crypto/cpu-intel.c')
-rw-r--r-- | crypto/cpu-intel.c | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/crypto/cpu-intel.c b/crypto/cpu-intel.c index 3dd08a9e..3f65e74d 100644 --- a/crypto/cpu-intel.c +++ b/crypto/cpu-intel.c @@ -66,15 +66,6 @@ #include <stdio.h> #include <inttypes.h> -/* This value must be explicitly initialised to zero in order to work around a - * bug in libtool or the linker on OS X. - * - * If not initialised then it becomes a "common symbol". When put into an - * archive, linking on OS X will fail to resolve common symbols. By - * initialising it to zero, it becomes a "data symbol", which isn't so - * affected. */ -uint32_t OPENSSL_ia32cap_P[4] = {0}; - /* OPENSSL_ia32_cpuid is defined in cpu-x86_64-asm.pl. */ extern uint64_t OPENSSL_ia32_cpuid(uint32_t*); |