| commit | bd20800c22fc8402611b537287bd6948c3f2a5a8 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Sep 29 14:53:42 2023 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 29 19:14:27 2023 +0000 |
| tree | 06fc7ae0baaef1eeff1749268733c74245f3f869 | |
| parent | d24a38200fef19150eef00cad35b138936c08767 [diff] |
Add a comment for what compiler_test.cc is about It's probably worth explaining in a comment that this is about implementation-defined behavior, and why we consider it okay to make assumptions like uint8_t == unsigned char. Change-Id: Ia35248aef7895b0998831b6bac06993e845e6297 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/63285 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> 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: