| commit | c7bec85f2b8e4daa28391c3805c87a3fc2ad1582 | [log] [tgz] |
|---|---|---|
| author | Eric Biggers <ebiggers@google.com> | Wed Mar 19 07:04:03 2025 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 19 15:20:44 2025 -0700 |
| tree | 121df1b057a11975fa32999225cbddd7cdad3034 | |
| parent | de614d890235236af3cf5ad6aa5ab762750f4a15 [diff] |
Rename avx10 and avx10_512 to avx512 Intel has made a late change to the AVX10 specification that removes support for maximum vector lengths other than 512 bits. Therefore, there won't be any such thing as AVX10/256. AVX10 will just be what was originally planned to be called AVX10/512, effectively just consolidating the AVX512 CPUID feature bits. In light of this development and the fact that the 256-bit support in aes-gcm-avx10-x86_64.pl didn't end up being used, the early adoption of the "avx10", "avx10_256", and "avx10_512" names no longer makes sense. So let's just use "avx512" instead. Rename file names and function names accordingly, and update some comments. No functional changes. Change-Id: I2d59912b72d5ca0679b0ea54ae770a672ca36dea Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/77847 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: