| commit | 9333d6df114dd0aa05802ec9c6c8c8e5075d39cd | [log] [tgz] |
|---|---|---|
| author | Brian Smith <brian@briansmith.org> | Tue Jan 26 14:32:46 2016 -1000 |
| committer | David Benjamin <davidben@google.com> | Wed Jan 27 22:08:26 2016 +0000 |
| tree | 4aa9fcccd0c0d88b751709249bc931877199bfdb | |
| parent | f5f4be8fac9ba7dd6766bb72a629bfed5d480021 [diff] |
Fix data <-> function pointer casts in thread_win.c. The uses of |memcpy| to cast pointer-to-function to pointer-to-data and back again did not have well-defined semantics. Use a union instead to avoid the need for such a conversion get well-defined semantics. Change-Id: I8ee54a83ba75440f7bc78c194eb55e2cf09b05d8 Reviewed-on: https://boringssl-review.googlesource.com/6972 Reviewed-by: David Benjamin <davidben@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: