| commit | 04b3a96452b57f74f9768b1126f35b7398ddfff3 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Wed Feb 08 21:08:49 2023 +0000 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 08 21:48:53 2023 +0000 |
| tree | 33925a9a1f92eaf754e89b2b4619cc0a4f86cfbd | |
| parent | 261ec612e21b81a4c16bbda615d0850556483b4f [diff] |
Revert "Drop HRSS assembly." This reverts commit 97873cd1a59b97ced00907e274afaff75edf4a57. In some configurations, Clang (when building for debug) compiles poly_mul_vec_aux with a huge (12KB) stack frame. It appears to be expanding the code into a huge SSA graph and then assigning every value in the graph to the stack. When optimising it can store the live values in only a few hundreds bytes of stack, but since this function recurses, the debug build can overflow the stack. Unclear quite what to do about this, but this change solves the immediate issue. Change-Id: Ifa531f91f10bf04de92e8d07fbb14c668b366454 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/57065 Auto-Submit: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: 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: