|author||Peter Collingbourne <email@example.com>||Wed Aug 07 16:30:50 2019 -0700|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Thu Aug 08 18:03:43 2019 +0000|
Add assembly support for -fsanitize=hwaddress tagged globals. As of LLVM r368102, Clang will set a pointer tag in bits 56-63 of the address of a global when compiling with -fsanitize=hwaddress. This requires an adjustment to assembly code that takes the address of such globals: the code cannot use the regular R_AARCH64_ADR_PREL_PG_HI21 relocation to refer to the global, since the tag would take the address out of range. Instead, the code must use the non-checking (_NC) variant of the relocation (the link-time check is substituted by a runtime check). This change makes the necessary adjustment in all of the places where it is needed when compiling with -fsanitize=hwaddress. While here, shrink the code by an instruction in each of those places by folding the addend into the load, and remove some dead code that seems to have been left over from commit 293d9ee4e837d122a28cd992e37779a5de48dc7f. We check for a sufficiently new clang before using the :pg_hi21_nc: relocation variant because support for this variant was only added recently. Change-Id: Ic9da8386e19c03c1e90c103a81232a254277e9a5 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/36924 Reviewed-by: Adam Langley <firstname.lastname@example.org> Commit-Queue: Adam Langley <email@example.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.
There are other files in this directory which might be helpful: