Google Git
Sign in
boringssl / boringssl / 2d94b5e1ee99a22c2fd3bb3b3dd5b4e3be6b3cc6
commit2d94b5e1ee99a22c2fd3bb3b3dd5b4e3be6b3cc6[log] [tgz]
authorEric Biggers <ebiggers@google.com>Tue Aug 20 23:24:14 2024 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 28 19:28:37 2024 +0000
treeffd5e1ed7f1af2d15860575d1246bbb806b4bcf8
parent824867d11061b2e7d03bd88c700093d3098373f8 [diff]
Support detecting AVX512BW, AVX512VL, VAES, and VPCLMULQDQ

Add helper functions that check the AVX512BW, AVX512VL, VAES, and
VPCLMULQDQ feature bits in the CPU capability words.  Also, make sure
that OPENSSL_cpuid_setup() clears VAES and VPCLMULQDQ when they are
unsupported due to the operating system not supporting ymm registers.

Change-Id: I2d672556acc269ef09ab6f5e080d37cb9831e7ce
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/68908
Commit-Queue: Bob Beck <bbe@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
Auto-Submit: Eric Biggers <ebiggers@google.com>
2 files changed
tree: ffd5e1ed7f1af2d15860575d1246bbb806b4bcf8
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. gen/
  7. include/
  8. pki/
  9. rust/
  10. ssl/
  11. third_party/
  12. tool/
  13. util/
  14. .bazelignore
  15. .bazelrc
  16. .clang-format
  17. .gitignore
  18. API-CONVENTIONS.md
  19. BREAKING-CHANGES.md
  20. BUILD.bazel
  21. build.json
  22. BUILDING.md
  23. CMakeLists.txt
  24. codereview.settings
  25. CONTRIBUTING.md
  26. FUZZING.md
  27. go.mod
  28. go.sum
  29. INCORPORATING.md
  30. LICENSE
  31. MODULE.bazel
  32. MODULE.bazel.lock
  33. PORTING.md
  34. PrivacyInfo.xcprivacy
  35. README.md
  36. SANDBOXING.md
  37. STYLE.md
README.md

BoringSSL

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: