diff options
author | Aaron Green <aarongreen@google.com> | 2018-02-12 13:07:28 -0800 |
---|---|---|
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | 2018-02-13 20:12:47 +0000 |
commit | 862e0d2e1b6524219a492873798a5b5c19589351 (patch) | |
tree | de1ad31adc1f7d37bf242afab92886b0acf23995 /PORTING.md | |
parent | 638a408cd267180ec42509b049d8112fdec2936b (diff) | |
download | boringssl-862e0d2e1b6524219a492873798a5b5c19589351.zip boringssl-862e0d2e1b6524219a492873798a5b5c19589351.tar.gz boringssl-862e0d2e1b6524219a492873798a5b5c19589351.tar.bz2 |
Add cpu-aarch64-fuchsia.c
Fuchsia/Zircon recently added support for exposing arm64 CPU features;
this CL uses the new system call to set OPENSSL_armcap_P.
Change-Id: I045dc0b58117afe6dae315a82bf9acfd8d99be1a
Reviewed-on: https://boringssl-review.googlesource.com/25865
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
Diffstat (limited to 'PORTING.md')
-rw-r--r-- | PORTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -210,7 +210,7 @@ strings and loading algorithms, etc. All of these functions still exist in BoringSSL for convenience, but they do nothing and are not necessary. The one exception is `CRYPTO_library_init`. In `BORINGSSL_NO_STATIC_INITIALIZER` -builds, it must be called to query CPU capabitilies before the rest of the +builds, it must be called to query CPU capabilities before the rest of the library. In the default configuration, this is done with a static initializer and is also unnecessary. |