| commit | de3c1f69cc8422f94e4415b34398f3be29fa1f83 | [log] [tgz] |
|---|---|---|
| author | Tom Tan <Tom.Tan@microsoft.com> | Thu Jan 10 13:44:42 2019 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jan 14 19:49:39 2019 +0000 |
| tree | fd1595f955881e01aad4989f62c68dce0949c45e | |
| parent | 2bee229103eec2d6c93e5e437c7fb5a51e299f72 [diff] |
Fix header file for _byteswap_ulong and _byteswap_uint64 from MSVC CRT _byteswap_ulong and _byteswap_uint64 are documented (see below link) as coming from stdlib.h. On some build configurations stdlib.h is pulled in by intrin.h but that is not guaranteed. In particular, this assumption causes build breaks when building Chromium for Windows ARM64 with clang-cl. This change switches the #include to use the documented header file, thus fixing Windows ARM64 with clang-cl. https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/byteswap-uint64-byteswap-ulong-byteswap-ushort Bug: chromium:893460 Change-Id: I738c7227a9e156c894c2be62b52228a5bbd88414 Reviewed-on: https://boringssl-review.googlesource.com/c/34244 Reviewed-by: David Benjamin <davidben@google.com> Reviewed-by: Bruce Dawson <brucedawson@chromium.org> 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.
There are other files in this directory which might be helpful: