| commit | f3d3cee4fedab2646d06603068b0dced68fdb49e | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Apr 21 17:23:11 2017 -0400 |
| committer | Adam Langley <agl@google.com> | Fri Apr 21 21:42:44 2017 +0000 |
| tree | 1fc93cd7a1dd6c77defd09d5b22d22a464238503 | |
| parent | 23ebe09eabba52d9a275e7cab39906ae9f2adb11 [diff] |
Avoid messing with dummy functions in delocate.go. With some optimisation settings, Clang was loading BORINGSSL_bcm_text_hash with AVX2 instructions, which weren't getting translated correctly. This seems to work and is less fragile. The compiler just emits an leaq here. This is because it knows the symbol is hidden (in the shared library sense), so it needn't go through GOTPCREL. The assembler would have added a relocation, were the symbol left undefined, but since we define the symbol later on, it all works out without a relocation. Were the symbol not hidden, the compiler would have emitted a movq by way of GOTPCREL, but we can now translate those away anyway. Change-Id: I442a22f4f8afaadaacbab7044f946a963ebfc46c Reviewed-on: https://boringssl-review.googlesource.com/15384 Reviewed-by: 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.
There are other files in this directory which might be helpful: