Searched refs:RPC (Results 1 – 10 of 10) sorted by relevance
16 add_definitions(-DTARGET_NAME=RPC)42 # Report to the parent scope that we are building a plugin for RPC.
22 #define TARGET_NAME RPC
201 for (ResourcePlusCycles &RPC : ID.Resources) { in initializeUsedResources()202 if (countPopulation(RPC.first) > 1 && !RPC.second.isReserved()) { in initializeUsedResources()204 uint64_t Mask = RPC.first ^ PowerOf2Floor(RPC.first); in initializeUsedResources()206 if (RPC.second.NumUnits > countPopulation(Mask)) { in initializeUsedResources()207 RPC.second.setReserved(); in initializeUsedResources()208 RPC.second.NumUnits = MaxResourceUnits; in initializeUsedResources()
2 - the XPC transport layer (alternative transport layer to JSON-RPC)
4 # Need to embed the correct temp path in the actual JSON-RPC requests.
328 - Communication and Transport (via JSON-RPC)337 client via JSON-RPC over stdin/stdout. In the code, this is the `JSONTransport`339 knows that JSON-RPC messages are coming in and JSON-RPC messages are going out.
438 RegisterCell RPC = RegisterCell::self(Reg[0].Reg, W0); in evaluate() local439 RPC.fill(0, 2, BT::BitValue::Zero); in evaluate()440 return rr0(eADD(RPC, eIMM(im(2), W0)), Outputs); in evaluate()
48 with the JIT via RPC.906 2. **ORC RPC based TargetProcessControl implementation**908 An ORC RPC based implementation of the ``TargetProcessControl`` API is
713 ORC provides a cross-process ``JITLinkMemoryManager`` based on an ORC-RPC-based717 channel is determined by the ORC-RPC channel type. Common options include unix
2304 "include/llvm/ExecutionEngine/Orc/RPC/*.h",