commit | 0eaf783fbf0abff42570f912737feefa084d1b3d | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Sun Dec 30 02:30:55 2018 +0000 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 02 23:49:24 2019 +0000 |
tree | 80dec9de1c866c814e8af54903642f59b674dca3 | |
parent | c2e8d016f5ae58b2df72db99250b31882b42b8ff [diff] |
Annotate leaf functions with .cfi_{startproc,endproc} While gdb can figure it out, libunwind requires CFI directives to unwind a leaf function, even though the directives are trivial. Adding them matches what GCC outputs, and likely gdb has many heuristics that less complex tools (e.g. profilers) may not. Bug: 181 Change-Id: I25c72152de33109a29710a828aeb99c608dd0470 Reviewed-on: https://boringssl-review.googlesource.com/c/33964 Commit-Queue: David Benjamin <davidben@google.com> 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: