Google Git
Sign in
boringssl / boringssl / 15596efa5fe18e43bdc0ecd32d4ef93437f51d49
commit15596efa5fe18e43bdc0ecd32d4ef93437f51d49[log] [tgz]
authorAdam Langley <agl@chromium.org>Mon Aug 01 18:29:34 2022 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Aug 01 19:39:25 2022 +0000
tree4f68073f89394819561674636c60a908daea9d7d
parentb7d6320be91bdf132349e8384bd779ffcff3f030 [diff]
Include hopefully all ARM instructions with condition codes.

We need to know which ARM instructions take a condition code because
otherwise the conditions look like symbols. This change includes all
instructions beginning with 'c' from [1] that include a `cond` argument.
Also sort them for easier comparison.

[1]
https://developer.arm.com/documentation/dui0802/a/A64-General-Instructions/CBNZ

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