commit | e2ff2ca0dcda4f37d9675f5d64add4a0ca239af9 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Mon Jun 12 18:10:33 2017 -0400 |
committer | David Benjamin <davidben@google.com> | Tue Jun 13 17:45:51 2017 +0000 |
tree | 51ea0346c0f98a5b55b8adddc103d6dae30059a9 | |
parent | 7f7ef53e6867495caa2296ea0c758a3b2d0af8e6 [diff] |
Revert "Use unified ARM assembly." This reverts commit 2cd63877b5d663d1f19dca08b36de9746c044f9d. We've since imported a change to upstream which adds some #defines that should do the same thing on clang. (Though if gas accepts unified assembly too, that does seem a better approach. Ah well. Diverging on these files is expensive.) This is to reduce the diff and make applying some subsequent changes easier. Change-Id: I3f5eae2a71919b291a8de9415b894d8f0c67e3cf Reviewed-on: https://boringssl-review.googlesource.com/17107 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: