| commit | e1379ff5eb8562274c3dbf68ce01fd5998fab356 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Mar 04 13:57:41 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 04 13:03:16 2025 -0800 |
| tree | 24c73cd48ecb2b4ea3a681dfc35533b13a195b4d | |
| parent | 7e529d2b3971c10d63c6a980f3744f580321ff40 [diff] |
Add local targets to .set directives in delocate Originally I thought the problem was that weak symbols need renaming, but actually delocate is fine with those. The local_target business (somewhat accidentally) routes around this problem. The problem is that GCC emits C1 and C2 constructors for unique_ptr as aliases of each other using .set foo, bar and we don't recognize that pattern as defining a symbol. The linker script version of this pipeline will need to do it with renaming instead, but we'll get to that later. Renaming symbols is actually quite annoying in delocate. Fixed: 397980180 Change-Id: I378c759c07a41af1155acf3f41889a0bd52b002f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/76967 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: 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: