|author||David Benjamin <firstname.lastname@example.org>||Sun Dec 16 00:03:53 2018 -0600|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Dec 17 17:54:07 2018 +0000|
Disable AES-GCM-SIV assembly on Windows. I'm working on a test harness to check our assembly correctly restores callee-saved registers. It caught this. While perlasm tries to smooth over the differences between Windows and SysV ABIs, it does not capture the difference in xmm registers. All xmm registers are volatile in SysV, while Windows makes xmm6 through xmm15 callee-saved. Change-Id: Ia549b0f126885768f7fb330271a590174c483a3d Reviewed-on: https://boringssl-review.googlesource.com/c/33685 Reviewed-by: Adam Langley <email@example.com> Commit-Queue: David Benjamin <firstname.lastname@example.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: