commit | 4f746a9073333d35db49173a8dbdc076004fa7d1 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue Nov 20 18:32:12 2018 -0600 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Nov 21 00:46:57 2018 +0000 |
tree | 4c84980859e3db95a9547e1e4298cef6decb7e8d | |
parent | a3ba8b3289e251ff29cbd88a69999ebea5fa492e [diff] |
Move ARM cpuinfo functions to the header. ClusterFuzz folks want to switch to a shared library build, so call into these another way. The new setup isn't quite ideal because the real code builds as C and now tests as C++, but it should work. Bug: chromium:907115 Change-Id: Ia1ffc18832739b09fee21b84ee5d181e61feaa15 Reviewed-on: https://boringssl-review.googlesource.com/c/33285 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@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.
There are other files in this directory which might be helpful: