Google Git
Sign in
boringssl / boringssl / a733dd89429b4c02a9a0591f4b6adfddc8e8c25f
commita733dd89429b4c02a9a0591f4b6adfddc8e8c25f[log] [tgz]
authorRudolf Polzer <rpolzer@google.com>Fri Oct 24 03:35:59 2025 -0700
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Oct 24 14:58:04 2025 -0700
tree463b07051e05f0d2e394fb7cb51137646dc69b84
parentea1b595f605f9ef371eb3e85802109370f6ad37a [diff]
Set `-fno-strict-aliasing` when building with bazel.

Repro: `bazel test -c opt ...` breaking `CompilerTest.NoStrictAliasing`.

This flag is already set in the CMake build system, and not setting it
in an optimized build causes at least that test to fail. Until
bug #42290308 is fixed, we should keep `-fno-strict-aliasing` enabled.

Bug: 42290308
Bug: 454835295
Change-Id: I602997d546e81b36b23104efc0c5a2a13d02d451
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/83227
Reviewed-by: David Benjamin <davidben@google.com>
Auto-Submit: Rudolf Polzer <rpolzer@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
1 file changed
tree: 463b07051e05f0d2e394fb7cb51137646dc69b84
  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. PRESUBMIT.py
  40. PrivacyInfo.xcprivacy
  41. README.md
  42. SANDBOXING.md
  43. 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: