| commit | 749d187063a6bc5e7f00847081dc444d002d3756 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Oct 20 13:00:51 2018 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Oct 24 00:55:44 2018 +0000 |
| tree | cd7ad3bf3fa58ff5e8697dc62dc254953b037007 | |
| parent | 127a1ec08020f3a8cb2c4d5d7716b74c7656578f [diff] |
Modernize OPENSSL_COMPILE_ASSERT. MSVC 2015 supports the static_assert keyword in C mode (not quite what C11 specifies: _Static_assert is the keyword and static_assert is a macro in assert.h, but close enough). GCC and Clang both support _Static_assert at all C versions. GCC has supported it in GCC 4.6. glibc supports the assert.h macro since glibc 2.16, but does condition it on the version, so we likely can't rely on that yet. Still, this means we should be able to rely on proper static assertions at this point. In particular, this means we'd no longer worry about emitting multiple typedefs of the same name. Though at some point, it'd be nice to rely on being built in C11 mode. Then we can just pull in assert.h and use bare static_assert, and the atomics business needn't be a build flag. Update-Note: If static asserts break the build, it's this CL's fault. Change-Id: I1b09043aae41242f6d40386c063e381d00b028d8 Reviewed-on: https://boringssl-review.googlesource.com/c/32604 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
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.
There are other files in this directory which might be helpful: