| commit | d95b03c315bac8c44d3ce062053d3a5817915d91 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Jul 27 10:19:40 2023 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 28 19:30:17 2023 +0000 |
| tree | 169d64b4fe57f717d3d2a215904beec714cd1426 | |
| parent | 0152f739622d40f3f05804c9a5217c849f903a89 [diff] |
Trim some redundant Arm feature detection files cpu_arm_openbsd.c is the same as OPENSSL_STATIC_ARMCAP. cpu_aarch64_freebsd.c is the same as cpu_aarch64_sysreg.c. (The FreeBSD one was using the macros in their headers, but those macros expand to the same inline assembly.) Also send ANDROID_BAREMETAL + 32-bit Arm to OPENSSL_STATIC_ARMCAP. This way we can remove OPENSSL_STATIC_ARMCAP from the Android baremetal build without having to chase down constraining it to aarch64. See b/291106677#comment6 Update-Note: This is a slight change to the OpenBSD build. Previously, we assumed OpenBSD on 32-bit Arm implies NEON. Now, we pick it up from the __ARM_NEON define from ACLE, i.e. whether the compiler has been told that NEON is available. (This comes from -march or other options.) Doing that is desirable anyway: if NEON is in your baseline, you should tell your compiler so it can vectorize loops. Change-Id: Icd43a2b56bb6e3f04f0fed996ae750fba65e3312 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/62066 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@google.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
Project links:
There are other files in this directory which might be helpful: