commit | 678c841cbe0a8980148d97913c25c730744261d8 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Fri Aug 10 08:53:34 2018 -0500 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Aug 10 14:18:28 2018 +0000 |
tree | 83b7d11a21d31e874287854b17337fe500a309c1 | |
parent | 4e446f27d05996309eec2ac1c2a71b66020cdfb2 [diff] |
Use -flto=thin in the CFI bot. The CFI bot is currently failing on a mysterious error message, coming from the recent clang roll. Called function is not the same type as the call! call void @EVP_MD_CTX_init(%struct.env_md_ctx_st* %8), !dbg !72123 LLVM ERROR: Broken function found, compilation aborted! Chromium actually passes -flto=thin, which seems to avoid the error, testing locally. Why it does, I haven't the slightest clue. The offending calls to EVP_MD_CTX_init (and EVP_MD_CTX_cleanup) are those buried in bssl::ScopedEVP_MD_CTX. However, not all calls are problematic, only the one in test_config.cc. What's more, if I add a call in async_bio.cc, linked into all the same targets, the copy in test_config.cc is suddenly fine!? Maybe there's just a bug in the LTO logic that ThinLTO avoids... Change-Id: I5266eec75edea2a38dee8ad5591db8d65d3bdede Reviewed-on: https://boringssl-review.googlesource.com/30805 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@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: