| commit | 5d54832f1a35ea4f3c7da1e92c205bb4591341d1 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <alangley@gmail.com> | Tue Dec 22 13:41:43 2020 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jan 11 19:03:16 2021 +0000 |
| tree | b33abf9cb6e71119e40c1b36e0c11d389a128204 | |
| parent | afd5dba756b6266fa99c11af6496b39d826769cd [diff] |
delocate: handle Aarch64 assembly in parser. Aarch64 assembly is quite different from x86-64 or POWER. But the system of directives is the same so there's quite a lot of utility from being able to use the same delocate framework. Unfortunately, with peg, there's no obvious way to be able to parse instructions differently without breaking the parsing into two stages. Thus the parser is extended here to support all three ISAs. This seems to work ok without breaking either of the other two. Change-Id: Iced0f651e556e6ffae3eb35f2edfc0bf84167967 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/44846 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: 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:
There are other files in this directory which might be helpful: