| commit | cd60bf0e0a5a710a90d68a7496ef9540305bfd32 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Jun 20 20:01:06 2017 -0400 |
| committer | Adam Langley <agl@google.com> | Thu Jun 22 02:37:19 2017 +0000 |
| tree | a94e11d54d4f7487e7fd184da0bbd06dd47e28f2 | |
| parent | 05d4c9727f30a0e0e687ba6646dac5e93a970a6c [diff] |
Fix PPC redirectors. Our old redirectors were emitting code to call their target functions normally. However, the PPC ABI expects callers to set up parameter save areas for their callees, notably if the target is a varargs function. Instead, mimic the pattern used when calling an external function or function pointer and avoid touching the stack. Change-Id: Ia28c9d2b82fcd99c4a2f70f5f587d0e0463a6f0e Reviewed-on: https://boringssl-review.googlesource.com/17284 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: