Google Git
Sign in
boringssl / boringssl / 672efb1f8ee029762e29ff16811b68a071a0528e
commit672efb1f8ee029762e29ff16811b68a071a0528e[log] [tgz]
authorAdam Langley <agl@imperialviolet.org>Sat Jan 13 14:01:32 2024 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jan 22 18:15:24 2024 +0000
treeb3871c6eb6d46695b9ac1e572197ccbc10458da1
parent4972efd0f964c3ae5de5085b7cfaecfb3f44833d [diff]
delocate: update to handle SVE2

Aarch64's SVE2 extension adds more syntax forms for registers, and a new
"tweak" pattern that means "multiply offset by the hardware's vector
length". This change tweaks delocate so that it can pass these forms.

See https://developer.arm.com/documentation/102340/0100/SVE2-architecture-fundamentals

Change-Id: I9a736dcf0b57d36d5e08a53e073da7fe3c62dea2
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65349
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
Auto-Submit: Adam Langley <agl@google.com>
4 files changed
tree: b3871c6eb6d46695b9ac1e572197ccbc10458da1
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. include/
  7. pki/
  8. rust/
  9. ssl/
  10. third_party/
  11. tool/
  12. util/
  13. .clang-format
  14. .gitignore
  15. API-CONVENTIONS.md
  16. BREAKING-CHANGES.md
  17. BUILDING.md
  18. CMakeLists.txt
  19. codereview.settings
  20. CONTRIBUTING.md
  21. FUZZING.md
  22. go.mod
  23. go.sum
  24. INCORPORATING.md
  25. LICENSE
  26. PORTING.md
  27. README.md
  28. SANDBOXING.md
  29. sources.cmake
  30. 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:

There are other files in this directory which might be helpful: