[all-commits] [llvm/llvm-project] 0cfd20: [JITLink][arm64][MachO] Apply PAC signing to __mod...

[Lang Hames via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 0cfd20ed1b8561a5d4587e8f624f9b4c8efd8b6f
      https://github.com/llvm/llvm-project/commit/0cfd20ed1b8561a5d4587e8f624f9b4c8efd8b6f
  Author: Lang Hames <lhames at gmail.com>
  Date:   2024-11-22 (Fri, 22 Nov 2024)

  Changed paths:
    M llvm/lib/ExecutionEngine/JITLink/MachO_arm64.cpp

  Log Message:
  -----------
  [JITLink][arm64][MachO] Apply PAC signing to __mod_init_func pointers.

The __mod_init_func section contains pointers to static initializer functions.
In the static compilation model for MachO/arm64e these are unsigned pointers
that are signed by dyld before being called. This patch teaches JITLink's
MachO/arm64 backend to sign __mod_init_func pointers using the PAC signing
function introduced in a432f11a52d (signing is triggered by rewriting all
Pointer64 edges in the section to Pointer64Authenticated edges). This means
that unlike the static compilation model the linked __mod_init_func section
will contain signed pointers.

Note: Signing of init pointers could instead have been handled by the ORC
runtime in a manner similar to dyld, but this would have come at the cost of
adding an extra signing oracle. Using the signing function avoids this.

Testing this change requires execution. It is covered by the
trivial-cxx-constructor.cpp testcase that was added to the ORC runtime in
7c0786363e6.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications