[llvm] [C-API] LLVMOrcCreateObjectLinkingLayerWithInProcessMemoryManager (PR #169862)
Thomas Munro via llvm-commits
llvm-commits at lists.llvm.org
Thu Nov 27 19:18:18 PST 2025
macdice wrote:
Let me lay out the motivation, so I can hopefully be corrected if I've misunderstood something:
* we want to use JITLink in order to
* drop our backported SectionMemoryManager that got us out of a nasty bind on AAarch64, taken from https://github.com/llvm/llvm-project/pull/71968
* run on newer platforms as discussed in https://github.com/llvm/llvm-project/issues/106203
* LLJIT still uses RuntimeDyld by default as of main today, per LLJIT.h's documentation of setObjectLinkingLayerCreator
* the default object linking layer will eventually change to JITLink, so one reason to need our own creator function will go away
* we'll still need a way to enable debugging and profiling support, so unless there's another way to inject the plugins we'll still need to control construction
Does this all make sense? Thanks!
https://github.com/llvm/llvm-project/pull/169862
More information about the llvm-commits
mailing list