|author||David Benjamin <firstname.lastname@example.org>||Sat Feb 02 21:29:58 2019 -0600|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Feb 05 19:22:15 2019 +0000|
Implement unwind testing for Windows. Unfortunately, due to most OpenSSL assembly using custom exception handlers to unwind, most of our assembly doesn't work with non-destructive unwind. For now, CHECK_ABI behaves like CHECK_ABI_NO_UNWIND on Windows, and CHECK_ABI_SEH will test unwinding on both platforms. The tests do, however, work with the unwind-code-based assembly we recently added, as well as the clmul-based GHASH which is also code-based. Remove the ad-hoc SEH tests which intentionally hit memory access exceptions, now that we can test unwind directly. Now that we can test it, the next step is to implement SEH directives in perlasm so writing these unwind codes is less of a chore. Bug: 259 Change-Id: I23a57a22c5dc9fa4513f575f18192335779678a5 Reviewed-on: https://boringssl-review.googlesource.com/c/34784 Commit-Queue: David Benjamin <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.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: