Google Git
Sign in
boringssl / boringssl.git / ddb002fc522a7ab7939a892862febcccd62f23e4
commitddb002fc522a7ab7939a892862febcccd62f23e4[log] [tgz]
authorBob Beck <bbe@google.com>Sat Mar 09 17:10:54 2024 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Mar 11 16:35:23 2024 +0000
tree2c09bc66722d51e02d3a01ea8ef2c304da321b01
parent29bb1a7ebe55102c90611c021a142fdb6e97f8d5 [diff]
Set -Wframe-larger-than=25344 for a typical cmake clang compile.

This ensures that in the "usual" development process building and
running the tests will enforce this stack limit, which is encountered
in google3. This will prevent future development from adding code
and tests which blow over this limit and break google3

Change-Id: If722c7029cca63eb7d1e80de4b640b84839bb020
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/66867
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Auto-Submit: Bob Beck <bbe@google.com>
1 file changed
tree: 2c09bc66722d51e02d3a01ea8ef2c304da321b01
  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: