Google Git
Sign in
boringssl / boringssl / 808b8f3b9d71a055f741d5f7338d206e98747950
commit808b8f3b9d71a055f741d5f7338d206e98747950[log] [tgz]
authorDavid Benjamin <davidben@google.com>Sat Mar 15 02:07:53 2025 +0700
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Mar 15 10:03:35 2025 -0700
treed0ab85159d6e7b29bf7a5c5fc96a3a703e000bf5
parent89eb6ddbf52887631ca45ad2242862515cd698ab [diff]
Remove bn_div_words from bn-586.pl

This function is unused. While there is a bn_div_words symbol, it's
static and we never actually use the assembly-defined one.

Not using it is potentially a missed optimization, but only for 32-bit
x86 on MSVC because for GCC/Clang we have inline assembly. (It is hard
for the compiler to emit the instruction itself because it cannot prove
that the division fits.)

Change-Id: Ia7ecd28f26143521343dd516a07eb3adf9c4378e
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/77627
Reviewed-by: Bob Beck <bbe@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
4 files changed
tree: d0ab85159d6e7b29bf7a5c5fc96a3a703e000bf5
  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: