| commit | 03d1b7c544851d9f44df1e9ff21839742e08c819 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Apr 06 11:46:21 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 10 21:35:29 2024 +0000 |
| tree | c82fe50f797a8b91ede9e00c1737f775a4dc92d2 | |
| parent | 6b36ad2bd6001f17a997b7a1e0ab254b001438ef [diff] |
Remove no-op register move from ChaCha20_ctr32_ssse3_4x r11 does not have anything in it yet, and r10 is never read. This is a remnant of the ia32cap dispatch that we missed in f5e0c8f92a22679b0cd8d24d0d670769c1cc07f3. Bug: 673 Change-Id: I5cc179401418aee6479b4a38ae1c09f68ec40238 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/68291 Commit-Queue: David Benjamin <davidben@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: