Google Git
Sign in
boringssl / boringssl / 3e2858d58b14cbc47d11a63e511892023ed6e82a
commit3e2858d58b14cbc47d11a63e511892023ed6e82a[log] [tgz]
authorEric Biggers <ebiggers@google.com>Mon Mar 17 21:41:15 2025 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Mar 17 17:36:13 2025 -0700
tree0d9705bded36c0ba31f9d68505cb548b83d84da4
parentc6292fa69a65ab116923993757eb2110db7799ba [diff]
Move gcm_gmult_vpclmulqdq_avx10 and add comment

Move the Perl code that generates gcm_gmult_vpclmulqdq_avx10() to
earlier in the file, so that it matches aes-gcm-avx2-x86_64.pl.  Also
add comments that explain why gcm_gmult_vpclmulqdq_avx2() and
gcm_gmult_vpclmulqdq_avx10() do not use vzeroupper.

No change to the generated assembly code except whitespace.

Change-Id: I74c7a7973f55bfd6a6c1663b9f20c0c7f178232c
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/77767
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
8 files changed
tree: 0d9705bded36c0ba31f9d68505cb548b83d84da4
  1. .bcr/
  2. .github/
  3. cmake/
  4. crypto/
  5. decrepit/
  6. docs/
  7. fuzz/
  8. gen/
  9. include/
  10. infra/
  11. pki/
  12. rust/
  13. ssl/
  14. third_party/
  15. tool/
  16. util/
  17. .bazelignore
  18. .bazelrc
  19. .bazelversion
  20. .clang-format
  21. .gitignore
  22. API-CONVENTIONS.md
  23. AUTHORS
  24. BREAKING-CHANGES.md
  25. BUILD.bazel
  26. build.json
  27. BUILDING.md
  28. CMakeLists.txt
  29. codereview.settings
  30. CONTRIBUTING.md
  31. FUZZING.md
  32. go.mod
  33. go.sum
  34. INCORPORATING.md
  35. LICENSE
  36. MODULE.bazel
  37. MODULE.bazel.lock
  38. PORTING.md
  39. PrivacyInfo.xcprivacy
  40. README.md
  41. SANDBOXING.md
  42. 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: