Lines Matching refs:remote
100 cl::opt<bool> RemoteMCJIT("remote-mcjit",
104 // Manually specify the child process for remote execution. This overrides
105 // the simulated remote execution that allocates address space for child
109 ChildExecPath("mcjit-remote-process",
111 "for remote MCJIT execution. If none is specified,"
314 // problems with remote targets (because lli's remote target support does not
449 errs() << "error: Remote process execution does not work with the "
531 // If the target is Cygwin/MingW and we are generating remote code, we
545 errs() << "warning: remote mcjit does not support lazy compilation\n";
580 // Sanity check use of remote-jit: LLI currently only supports use of the
581 // remote JIT on Unix platforms.
584 errs() << "Warning: host does not support external remote targets.\n"
589 errs() << "-remote-mcjit requires -mcjit-remote-process.\n";
643 // Remote target MCJIT doesn't (yet) support static constructors. No reason
647 // Lanch the remote process and get a channel to it.
650 errs() << "Failed to launch remote JIT.\n";
654 // Create a remote target client running over the channel.
655 typedef orc::remote::OrcRemoteTargetClient<orc::remote::RPCChannel> MyRemote;
658 // Create a remote memory manager.
662 // Forward MCJIT's memory manager calls to the remote memory manager.
666 // Forward MCJIT's symbol resolution calls to the remote.
677 // Grab the target address of the JIT'd main function on the remote and call
686 // Like static constructors, the remote target MCJIT support doesn't handle
690 // with the remote, otherwise it'll crash when it tries to release resources
691 // on a remote that has already been disconnected.
694 // Signal the remote target that we're done JITing.
