| commit | ff2394527fd863741b75d160836d2badd4346a43 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Fri Jun 09 16:52:00 2017 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat Jun 10 00:00:58 2017 +0000 |
| tree | ef2a461e61fac5712fe70f60679f1f0708bb7a5e | |
| parent | 18d9f28f0df9f95570f233f47a8570c865706fe4 [diff] |
ppc64le delocate: avoid r0 as a base register. On POWER, r0 is wired to zero in some argument positions of some instructions. The base register for a load is one of them. Thus, if rewriting a load to r0, we cannot use r0 to store the base address. This could be more efficient, but loading to r0 appears to be very rare so I'm not going to worry about it for now. Change-Id: I14dac96ba4c0380b166a7667b0cba918f1ae25ec Reviewed-on: https://boringssl-review.googlesource.com/17065 Commit-Queue: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: 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: