| commit | a306b1b908cacf49d17cf77437d38da98ca5edcf | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Dec 30 02:14:33 2018 +0000 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 02 23:39:21 2019 +0000 |
| tree | fe343f990ef43cc2085b01ca2a7a7581e405538e | |
| parent | 6ef1b6455821f0d1c6b61ba91ba0cadd374d4049 [diff] |
Fix CFI annotations in p256-x86_64-asm.pl. This was caught by in-progress work to test unwind information. It was incorrect at two instructions: immediately before we jump to .Lpoint_double_shortcut$x. This is needed because ecp_nistz256_point_add$x tries to be clever about not unwinding the stack frame in its tail call. It's also unlikely that the SEH handlers in this file are correct at this point, but that will be handled separately while overhauling everything else here. (For Win64, probably the only ABI-compliant option is to just properly unwind the stack frame. Without a custom handler, Win64 unwind codes are very restrictive.) Bug: 181 Change-Id: I9f576d868850312d6c14d1386f8fbfa85021b347 Reviewed-on: https://boringssl-review.googlesource.com/c/33946 Commit-Queue: David Benjamin <davidben@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: