| commit | c556d87ddfe836294c8e04fc59d0c298951a4cc7 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Jan 06 17:50:44 2020 -0500 |
| committer | Adam Langley <agl@google.com> | Mon Jan 13 19:14:52 2020 +0000 |
| tree | 41310c265a9dcb12bd2f61616c004efa22f8514c | |
| parent | 3e96cd4b768e1ebba33327d2c3b7f6d4b8c1c5f6 [diff] |
Reland bitsliced aes_nohw implementation. This relands https://boringssl-review.googlesource.com/c/boringssl/+/39206. See that CL description for details on the change. The CL was originally reverted due to a number of ARM-only test failures. First, there was a test-only issue, resolved in https://boringssl-review.googlesource.com/c/boringssl/+/39306. Second, the implementation did not work in unoptimized Android Thumb2 builds. This was caused by a clang bug introduced in https://reviews.llvm.org/rL340261 and fixed in https://reviews.llvm.org/rL351310. aes_nohw_(un)compact_block have been rewritten in an attempt to dodge the bug. Performance of optimized builds with clang and gcc do not appear to be affected by the rewrite. See the delta from patch set 1. (I had hoped to improve precommit CQ coverage before landing this, but both failures turned out to be ARM-only. Either way, there are now 32-bit and 64-bit SSE2-less configurations so the 32-bit and 64-bit implementations have CQ coverage.) Change-Id: If5f9f5ea570686a15258ecd7cf49bdbc12dc34c5 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39444 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.
Project links:
There are other files in this directory which might be helpful: