| commit | 2e819d8be47e4b3b1fed719b5db918539240eff9 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Feb 06 04:33:38 2019 +0000 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Feb 12 20:24:27 2019 +0000 |
| tree | 9146dd0e7e3f19503aed5688a7b47ec96e99bd62 | |
| parent | 15ba2d11a9873cb40b2a45bba18242fdb16ca4c6 [diff] |
Unwind RDRAND functions correctly on Windows. But for the ABI conversion bits, these are just leaf functions and don't even need unwind tables. Just renumber the registers on Windows to only used volatile ones. In doing so, this switches to writing rdrand explicitly. perlasm already knows how to manually encode it and our minimum assembler versions surely cover rdrand by now anyway. Also add the .size directive. I'm not sure what it's used for, but the other files have it. (This isn't a generally reusable technique. The more complex functions will need actual unwind codes.) Bug: 259 Change-Id: I1d5669bcf8b6e34939885d78aea6f60597be1528 Reviewed-on: https://boringssl-review.googlesource.com/c/34867 Commit-Queue: Adam Langley <agl@google.com> 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: