Lines Matching refs:executor

35    into a target *executor* process.
48 calls JITLink's ``link`` function to link the graph into the executor process.
79   emitted to the executor process. It can be overridden to finalize state
200   in the executor process's virtual address space.
405   * ``getTargetTriple`` returns an `llvm::Triple` for the executor process.
407   * ``getPointerSize`` returns the size of a pointer (in bytes) in the executor
410   * ``getEndinaness`` returns the endianness of the executor process.
543       Calls the ``JITLinkMemoryManager`` to copy working memory to the executor
661 since the memory manager must know how to communicate with the executor, and
695   Should be overridden to return the address in the executor's address space of
723 JITLink's ability to link JIT'd code for a separate executor process can be
724 used to improve the security of a JIT system: The executor process can be
736 as RW- in the JITLink process and R-X in the executor process, allowing
737 modification from the JITLink process but not from the executor (at the cost of
762 non-trivial action in the executor (e.g. running initializers, managing thread
766 between the runtime (which executes in the executor process) and JITLink (which
768 must be taken in the executor). For example: Execution of MachO static
937 Remote execution via llvm-jitlink-executor
943 The ``-oop-executor[=/path/to/executor]`` option tells ``llvm-jitlink`` to
944 execute the given executor (which defaults to ``llvm-jitlink-executor``) and
945 communicate with it via file descriptors which it passes to the executor
948 The ``-oop-executor-connect=<host>:<port>`` option tells ``llvm-jitlink`` to
949 connect to an already running executor via TCP on the given host and port. To
950 use this option you will need to start ``llvm-jitlink-executor`` manually with
1047 The ``-oop-executor`` and ``-oop-executor-connect`` options are helpful for testing