| commit | 6ce93ccb8087109a9c1444746402fcae1b12867a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Oct 31 14:48:23 2018 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Nov 15 00:58:09 2018 +0000 |
| tree | 57660b161b375579f1e9d78cb336c59bd63fa266 | |
| parent | 444c2e59fbc52b87085e1afdf7b6c19a0ed4a894 [diff] |
Simulate other ARM CPUs when running tests. We test all Intel variants via SDE. For ARM, we can do the next best thing and tweak with OPENSSL_armcap_P. If the host CPU does not support the instructions we wish to test, skip it, but print something so we know whether we need a more featureful test device. Also fix the "CRASHED" status to "CRASH", to match https://chromium.googlesource.com/chromium/src/+/master/docs/testing/json_test_results_format.md (It's unclear if anything actually parses that JSON very carefully...) Bug: 19 Change-Id: I811cc00a0d210a454287ac79c06f18fbc54f96dd Reviewed-on: https://boringssl-review.googlesource.com/c/33204 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 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: