| commit | a6c42d6810ea5317fe8ed85704c097cd8f3513ca | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Jun 08 08:42:06 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 10 17:21:00 2024 +0000 |
| tree | eb5fc5cfde7656c60f127600872fe5a046fd8923 | |
| parent | 56fb43a204e57af68e00f4561c108a7004381aa3 [diff] |
Remove Knights Landing and Knights Mill logic Intel has removed support for Knights Landing and Knights Mill chips (Xeon Phi) from GCC, LLVM, and SDE. The last of which means we can no longer test the special-case to optimize for them. These special cases date to OpenSSL's 64d92d74985ebb3d0be58a9718f9e080a14a8e7f, which describes it as a "salvage operation" because they have Silvermont-like performance issues and "ADCX/ADOX instructions are effectively mishandled at decode time". In principle, this is not very much code to continue "salvaging" them, but we don't like having code we cannot test, so follow Intel's lead in removing all support. With this change, Xeon Phi chips should keep working (assuming their CPUID reports capabilities accurately), but will likely perform much worse. This should unbreak the SDE builders on CI. Change-Id: I00c3c435222fc53c1a6c9fddf961146f837dee7d Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/69187 Commit-Queue: Bob Beck <bbe@google.com> Auto-Submit: 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: