| commit | c2897a158a02a05a4d7d1115e1d81f34166ef729 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Tue Dec 18 08:41:34 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Dec 18 17:06:48 2018 +0000 |
| tree | 2cd0ae6873aaeb07182d57dabc59321682a5bd13 | |
| parent | f8068ce88574b36be69bd24d72290c9c3f5ceaf2 [diff] |
Don't enable intrinsics on x86 without ABI support. At some point after GCC 7.3, but before 8.2, GCC enabled the SSE ABI by default. However, if it isn't enabled, the vector intrinsics in HRSS cannot be used. (See https://github.com/grpc/grpc/issues/17540.) Note that the intrinsics used are SSE2, but that should be ok because they are guarded by a run-time check. The compile-time check for __SSE__ just ensures that GCC will build the code at all. (SDE does not simulate anything that doesn't have SSE2, however.) Change-Id: If092a06a441ed9d38576ea30351b3b40693a3399 Reviewed-on: https://boringssl-review.googlesource.com/c/33744 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@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.
There are other files in this directory which might be helpful: