| commit | cb42354ac373ad280ce33ee1b04ece0fc8bb1052 | [log] [tgz] |
|---|---|---|
| author | Brian Smith <brian@briansmith.org> | Thu Dec 22 17:13:59 2016 -1000 |
| committer | Adam Langley <alangley@gmail.com> | Fri Jan 13 01:22:26 2017 +0000 |
| tree | daf39431909a86cfe172f7509859d4c5d28bd65a | |
| parent | 18a37a4211c6cb81b2e28fa619b713e5b8a9a56c [diff] |
Clarify x86 GCM asm implementation dispatching. There is no AVX implementation for x86. Previously on x86 the code checked to see if AVX and MOVBE are available, and if so, then it uses the CLMUL implementation. Otherwise it fell back to the same CLMUL implementation. Thus, there is no reason to check if AVX + MOVBE are enabled on x86. Change-Id: Id4983d5d38d6b3269a40e288bca6cc51d2d13966 Reviewed-on: https://boringssl-review.googlesource.com/13024 Reviewed-by: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <alangley@gmail.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: