| commit | 43c279f17c03a44ee97ab5cd3e9e129e3e00609e | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Mar 11 16:33:24 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 11 14:05:04 2025 -0700 |
| tree | 92c2fe7cd78a5cf904b15c36c1165e9d7a8de55d | |
| parent | e1d6cd95a545569339a13d71b9ce5b92859214d9 [diff] |
Stop manually encoding a bunch of x86-64 instructions The perlasm code used to manually encode some instructions, presumably to accomodate older assemblers that don't recognize them. The newest of these (SHA instructions) seem to have been added in binutils 2.24, released in 2013. Remove the transforms so we don't have to worry about bugs in some ad-hoc perl code. I confirmed this was equivalent by comparing the output of `objdump -d` on the assembled object files. This revealed one issue in the xlate script where it tried to suffix rdrand, which is apparently unsuffixable. Change-Id: I51377e38ec06b099e730da29b85743188abf9723 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/77388 Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: David Benjamin <davidben@google.com> Auto-Submit: David Benjamin <davidben@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: