| commit | d43fef7cd52fc6c689ee919b2e97fff920a4c18c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Jul 12 20:48:55 2023 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 13 01:26:16 2023 +0000 |
| tree | e98984e9caf006ad675ee120edbee573a645dc95 | |
| parent | b98ce18c5b3f0c28bd64b27b6494f176404da4e4 [diff] |
Fix aarch64 build with GCC GCC does not have __has_feature, so writing #if __has_feature(foo), without a guard, will cause GCC to error. This is tripping the gRPC update. Prior to https://boringssl-review.googlesource.com/c/boringssl/+/60765, this worked because the preamble to every assembly file would define the missing __has_feature macro as part of detecting MSan. Now we pick up the logic in <openssl/base.h>, which tries not to stomp over symbols we don't own. This had the side effect of removing the __has_feature polyfill. Though "public", <openssl/asm_base.h> is not really a public header, so we could put the __has_feature polyfill in there. But we already have a pattern for detecting sanitizers in <openssl/target.h>, so just switch to that one. Change-Id: I747b4513f1b2f189d2df629149f22fd0fa490257 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/61565 Commit-Queue: Adam Langley <agl@google.com> Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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: