| commit | 22ac2d9b258c0769d1a989fa8ad81521ca7777e5 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jul 20 10:07:56 2018 -0400 |
| committer | Adam Langley <agl@google.com> | Mon Jul 23 19:07:41 2018 +0000 |
| tree | efbec2c36b84d5067ada1c24365424decc9b6145 | |
| parent | fc04cb217d79b3a1edca7f846547934ca04d417d [diff] |
Fail the build if MSan is built with assembly. MSan works by instrumenting memory accesses in the compiler. Accesses from uninstrumented code, such as assembly, are invisible to it. MSan will incorrectly report reads from assembly-initialized memory as uninitialized. To avoid confusing downstream consumers with false positives, catch this at compile-time with a more useful error. Update-Note: BoringSSL with MSan and assembly doesn't work, but now rather than crashing at runtime, it will fail to build altogether. It's possible someone was building BoringSSL with MSan and either not running it at all or just not exercising the codepaths that break. Bug: 252 Change-Id: I0c8b0fa3c2d1e584b3f40d532a668a8c9be06cb7 Reviewed-on: https://boringssl-review.googlesource.com/29928 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.
There are other files in this directory which might be helpful: