| commit | edfe4133d28c5e39d4fce6a2554f3e2b4cafc9bd | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Mar 22 16:28:22 2021 -0400 |
| committer | Adam Langley <agl@google.com> | Tue Mar 23 17:32:33 2021 +0000 |
| tree | d9a5d244759b142367617efeddfe5217fe44be33 | |
| parent | 565081680a6b432a5ddc275fcf2b11375a97f39c [diff] |
Automatically enable C11 atomics when available. It's now 2021. Hopefully we can at least assume anyone building with -std=c11 also has a corresponding set of headers. Plus, even if you don't, Clang seems to provide a header. (So C11 atomics work in clang-cl.) Also apparently atomics are optional, so this checks __STDC_NO_ATOMICS__. This does *not* set C11 as the minimum version. If you build with -std=c99, we'll silently use the non-atomics implementation. That's a little magical, so I've kept OPENSSL_C11_ATOMIC as a way to assert that you really want C11 atomics. Mostly it turns into a -std=c11 && !MSVC self-assert. Update-Note: If something fails to compile, we'll revert this and adjust the check, or add an opt-out, or give up. Also, if building with -std=c99, consider -std=c11. Change-Id: I1a8074c367a765c5a0f087db8c250e050df2dde8 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/46344 Reviewed-by: Adam Langley <agl@google.com>
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: