| commit | abd7077230a20b7ec465a8174088e5213b55eab5 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@chromium.org> | Wed Dec 11 14:44:53 2024 -0800 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Dec 12 11:45:12 2024 -0800 |
| tree | 60f11b020c1c97bbd17fe8b590cc4e431e446d68 | |
| parent | 830e786772558fa9b80aa7e7118aaa5b2a042344 [diff] |
delocate: support floating point literals in AArch64 asm. fcmp supports comparing a register against zero without needing to load zero into a register. This is expressed in the asm as: fcmp d0, #0.0 I.e. a literal floating-point zero, which delocate cannot currently parse. LLVM starts generating such instructions with [1]. [1] https://github.com/llvm/llvm-project/commit/97ff96173abc0e914d5c8716ccc6356342aca043 Bug: 383435112 Change-Id: I9c2cdd9f3377f56ba56a7287beed26061c2ac98f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/74227 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@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: