| commit | 469118ca637887427f9727f1aac13c3e5bdee068 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Jan 27 18:54:15 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 21 18:00:51 2024 +0000 |
| tree | eddd2289dde094314b9494481b37cfeac098a6ba | |
| parent | 90f0f05cca750b74c29c4ae8ee1ed800effa23c0 [diff] |
Move capability checks in sha256-586.pl to C This took a little restructuring because they were previously all one big function. Some notes: - label() and set_label() in x86 perlasm default to function-scoped. But static_label() marks a label as file-scoped, which is why "pic_point" and "K256" work. - There's a pretty sizeable common preamble. I just copied it to each for simplicity. I'm pretty sure some of it is wasted, but it's definitely not all wasted, between loading parameters, setting up stack alignment, and saving the old stack location. But I'm not sure if all those 16 bytes are actually used. Bug: 673 Change-Id: I6e8671d05d07cb4676ecf117dd56e2ed355c5d19 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65874 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@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.
Project links:
There are other files in this directory which might be helpful: