Google Git
Sign in
boringssl / boringssl / b803ed04706c772335abce3fb8b2c1cc43ca2cd4
commitb803ed04706c772335abce3fb8b2c1cc43ca2cd4[log] [tgz]
authorEric Biggers <ebiggers@google.com>Fri Mar 07 11:34:55 2025 -0800
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Mar 10 14:57:15 2025 -0700
tree8f2bca24fbf1f8269e8f0a709740d1617e454736
parent298ac78507178d1e7d058eee1e52333f760eb0c1 [diff]
aes-gcm-avx10-x86_64.pl: use strict mode and sync with avx2 code

Make aes-gcm-avx10-x86_64.pl run in perl's strict mode, like
aes-gcm-avx2-x86_64.pl does.  Also bring in some of the other
non-functional changes to the perl code in the avx2 version, like naming
V0-V3 as AESDATA0-AESDATA3 in the en/decryption function.

No change to the generated assembly code except whitespace.

Change-Id: I5857cfdcc881a34c971959a1962dfb181eb11450
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/77168
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
4 files changed
tree: 8f2bca24fbf1f8269e8f0a709740d1617e454736
  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: