|author||David Benjamin <email@example.com>||Sun Feb 03 19:18:11 2019 +0000|
|committer||Boringssl LUCI CQ <firstname.lastname@example.org>||Fri Jan 20 23:41:48 2023 +0000|
Add initial support for SEH directives in x86_64 perlasm This implements similar directives as MASM, so we do not need to build all the structures by hand. It does not provide any help to abstract between Win64 and SysV differences, however. This is pulled together from some old draft CLs I had, one of which actually synthesized CFI directives from SEH, so it should be possible. I've intentionally omitted that however, as it also brings in questions about how to handle the calling convention differences (the existing machinery won't *quite* work). I've uploaded just this for now, so review can focus on the basic mechanism. I've also preserved perlasm's weird mixed tabs and spaces indentation convention for now, though it is a bit tedious. Bug: 259 Change-Id: Ib3f46a27751a5319b758d12c462c660cf9f3e632 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/56126 Auto-Submit: David Benjamin <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org> Commit-Queue: Adam Langley <email@example.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: