Google Git
Sign in
boringssl / boringssl / 6b36ad2bd6001f17a997b7a1e0ab254b001438ef
commit6b36ad2bd6001f17a997b7a1e0ab254b001438ef[log] [tgz]
authorDavid Benjamin <davidben@google.com>Thu Apr 04 01:45:49 2024 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 10 20:28:10 2024 +0000
tree8fafdc4fd42c2338867539e9fbbde217e304b4a3
parent1d24e04c7143171ae2010c842e3e1438510fd1c0 [diff]
Re-remove redundant OPENSSL_IA32_SSE2 from perlasm commands

See https://boringssl-review.googlesource.com/c/boringssl/+/65869. I
accidentally reintroduced them with the new tool due to a mismerge.
(This doesn't change the output.)

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