|author||David Benjamin <firstname.lastname@example.org>||Wed Aug 09 00:44:48 2017 +0000|
|committer||David Benjamin <email@example.com>||Wed Aug 09 00:44:58 2017 +0000|
Revert "Enable ADX in x86_64-mont*.pl." This reverts commit 83d1a3d3c81c119f0fa7504525a6822b82790da0. Reason for revert: Our Windows setup can't handle these instructions. Will investigate tomorrow, possibly by turning ADX off on Windows. Change-Id: I378fc0906c59b9bac9da17a33ba8280c70fdc995 Reviewed-on: https://boringssl-review.googlesource.com/19004 Reviewed-by: David Benjamin <firstname.lastname@example.org>
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: