| commit | f2a3aae4ac4d914d9fb8587ee7d1a7756bbc66c3 | [log] [tgz] |
|---|---|---|
| author | Brian Smith <brian@briansmith.org> | Tue Dec 05 19:00:21 2023 -0800 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 12 16:22:37 2023 +0000 |
| tree | 1a58fb8db55e4a43ae4588c1546f3b0622a89242 | |
| parent | 9e40481d5bfe08e3e6daa5335c2cf076e1187ec1 [diff] |
sha: Remove check for SSSE3 for AVX variants. I verified using Intel XED that all the non-base instructions are classified as AVX for the _avx variants or AVX/AVX2/BMI/BMI2 for sha1_block_data_order_avx2. Change-Id: Id0b744369ff81521d33230bf337e4dff963aecd4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/64547 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Bob Beck <bbe@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: