tree 644d7cf0d152815fc79ae337ade378180b33c8dd
parent a82b97c524e851b0807b95c34a2154a2cbce9bdf
author Thomas Munro <thomas.munro@gmail.com> 1764818527 +1300
committer GitHub <noreply@github.com> 1764818527 +1100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJpMP5fCRC1aQ7uu5UhlAAA1T4QAITy1VlJm+xCiNDNMRbKpLkl
 T2lcFvcDSqDvUjWEtCnBKQLCEbd8SjLfTT9IvgAdNuiKEmhUaw8llSIwEq5zQl8N
 E4RPaOfgCKafst8p6DGuySzDkieqQvRtsoSyE6EhAPS79HuX9eKRxqKncSh7fIK/
 uuU06YG2yAeeMqzPD+LxXsNpllBQjhN5T/2ECsmPlATEsPkkOxyjsGm/XQkJ9So/
 iIkOfsoLPPp3A0xRKFz8p9fTAQA2zsgMt/qkqAltw7XpWVafwhOSdJ/MqWRbTuwA
 p0Kkde4wUFRDouPfsYuf9JDEE6CQyB5+VD6QLjyni9RQoz/JOkliriJBwF/72HrE
 j9+vAkU44UbTXYVWM9yokJxrvt96wQ2Zmt7wO2LGYnuPpkLFFWdp9Jh0qkttjbbV
 N4DdA9pjp3QkRoPVZG3Y69KIJKydAXSI3g8M5VulDiWz6ARLcLAWsW7PSL/SamvK
 ETvf+slyhogHAbCArGJi7MWq4M+wsuXlusgZ7A0sLVusOIuHjAHpAjjI/pPZ+Gen
 5jlfX0YTFD4ZllCe4O9Lnpp3+VU/cMNLY8JESyeI5V08bo2F/qo/wuRuxjUosfjD
 CpO9+JJp1orGTzNPfBJ1yXG5WorRU+As8YuZdh+iFJWi6vCwdQforXwzpY7BiHEh
 IPoM+n0VaD7s4FJYrSQo
 =X7ju
 -----END PGP SIGNATURE-----
 

[C-API] LLVMOrcCreateObjectLinkingLayerWithInProcessMemoryManager (#169862)

Allow C programs to use JITLink with trivial new C-API wrapper. Modeled
on `LLVMOrcCreateRTDyldObjectLinkingLayerWithSectionMemoryManager`
except that it has to deal with failure of
`jitlink::InProcessMemoryManager::Create()`. Function name suggested by
@lhames in https://github.com/llvm/llvm-project/issues/106203.

I suppose failure of underlying platform-specific things like
`sysconf(_SC_PAGESIZE)` shouldn't really happen. An alternative error
reporting style might be to follow
`LLVMOrcCreateDynamicLibrarySearchGeneratorForProcess` and return
`LLVMErrorRef` with an output parameter for the `LLVMOrcObjectLayerRef`,
but then it wouldn't be a drop-in replacement for
`LLVMOrcCreateRTDyldObjectLinkingLayerWithSectionMemoryManager`.
Thoughts?

This is wanted by PostgreSQL (branch using this API:
https://github.com/macdice/postgres/tree/llvm-22-proposed-c-api). (We're
also using `LLVMCreatePerfJITEventListener`,
`LLVMCreatePerfJITEventListener`,
`LLVMOrcRTDyldObjectLinkingLayerRegisterJITEventListener`, so it looks
like we'll need to research `PerfSupportPlugin`,
`DebuggerSupportPlugin`, `ObjectLinkingLayer::addPlugin()`...)