[all-commits] [llvm/llvm-project] 4695d9: [ORC] Generalize RTBridge Callers to any runtime f...

[Lang Hames via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 4695d911c68df381d3a1b088570bca8bc0c6bf23
      https://github.com/llvm/llvm-project/commit/4695d911c68df381d3a1b088570bca8bc0c6bf23
  Author: Lang Hames <lhames at gmail.com>
  Date:   2026-08-02 (Sun, 02 Aug 2026)

  Changed paths:
    M llvm/include/llvm/ExecutionEngine/Orc/RTBridge/Calls.h
    M llvm/include/llvm/ExecutionEngine/Orc/RTBridge/SPS/Calls.h

  Log Message:
  -----------
  [ORC] Generalize RTBridge Callers to any runtime function (#213526)

An RTBridge Caller is a controller-side handle for calling a function in
the runtime. Until now the abstraction assumed every such function was a
trampoline -- a runtime function whose job is to invoke *another*
function at an address the controller supplies (run-as-main, run-as-int,
etc.) -- so every Caller carried a dedicated ExecutorAddr parameter for
that target.

Generalize Callers to call runtime functions of any shape. Invoking a
supplied target is now just one kind of call, with the target address an
ordinary leading argument rather than a built-in parameter: e.g.
MainCaller becomes Caller<int64_t(ExecutorAddr, ArrayRef<std::string>)>.

The SPS signatures already led with an SPSExecutorAddr for the target,
so this is a pure interface change -- the SPS wrappers and all call
sites are unaffected. It lets Callers model runtime functions that do
the work themselves, such as the memory-access wrappers, rather than
only those that dispatch to another function.



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