Since the last update all in-tree tools and examples that support remote-JITing have been moved from OrcRPCExecutorProcessControl (and the older OrcRemoteTarget* APIs) to SimpleRemoteEPC. SimpleRemoteEPC, compared to earlier APIs, should be both easier to use and adapt, and better at error handling and recovery.
You can check out an example use of SimpleRemoteEPC in the llvm-jitlink tool, in the Session::Create method . In that method the “if” sequence constructs the ExecutorProcessControl object to be used, using a SimpleRemoteEPC instance for remote executors (in the -oop-executor or -oop-executor-connect case). By writing the llvm-jitlink tool against the ExecutorProcessControl API these few lines are all that it takes to dynamically select in-process or out-of-process JITing.
The corresponding server-side code can be found in the llvm-jitlink-executor tool’s main method .
The switch to SimpleRemoteEPC has allowed us to remove all in-tree users of the ORC RPC system, two of the more complicated JITLinkMemoryManager implementations, and the ORC RPC system itself. All up ~6.5k SLOC were removed in this process. Removing this legacy code should unblock progress on the JITLinkMemoryManager refactor – I hope to have an update on that effort for you next week.