Google Git
Sign in
boringssl / boringssl / eae890f1ba6dba5b2d37db9eecfbcb8544f94070
commiteae890f1ba6dba5b2d37db9eecfbcb8544f94070[log] [tgz]
authorDavid Benjamin <davidben@google.com>Fri Sep 13 12:41:22 2024 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Sep 13 16:56:14 2024 +0000
treed25a128da26c1f11e07adb6242a7882abc665cf8
parent642e8e56de35590ba56046a880b8e3620d11ec9b [diff]
Fix delocate with the aarch64 NO_ASM build

This compiler sometimes emits code like this:

	adrp x10, .Llocal_data2+16
	ldr q0, [x10, :lo12:.Llocal_data2+16]

We transform it into:

	adr x10, .Llocal_data2+16
	ldr	q0, [x10]

Note this makes some assumptions on the compiler, which I've documented
in comments. We already have a similar assumption on ADRP + ADD pairs,
but it is a little more likely for the compiler to do this in the ADRP +
LDR case.

Hopefully we can get the delocate replacement working soon and make all
this moot.

Change-Id: Icf4ed701142a52edf38d285c0bc5d52c17032d4f
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71267
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: Adam Langley <agl@google.com>
3 files changed
tree: d25a128da26c1f11e07adb6242a7882abc665cf8
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. gen/
  7. include/
  8. pki/
  9. rust/
  10. ssl/
  11. third_party/
  12. tool/
  13. util/
  14. .bazelignore
  15. .bazelrc
  16. .clang-format
  17. .gitignore
  18. API-CONVENTIONS.md
  19. BREAKING-CHANGES.md
  20. BUILD.bazel
  21. build.json
  22. BUILDING.md
  23. CMakeLists.txt
  24. codereview.settings
  25. CONTRIBUTING.md
  26. FUZZING.md
  27. go.mod
  28. go.sum
  29. INCORPORATING.md
  30. LICENSE
  31. MODULE.bazel
  32. MODULE.bazel.lock
  33. PORTING.md
  34. PrivacyInfo.xcprivacy
  35. README.md
  36. SANDBOXING.md
  37. STYLE.md
README.md

BoringSSL

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: