RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-22 10:42:39 +01:00
Code Issues Projects Releases Wiki Activity
master
llvm-mirror/unittests/ExecutionEngine/Orc/CMakeLists.txt

39 lines
786 B
CMake
Raw Permalink Normal View History

[Orc] Re-add C bindings for the Orc APIs, with a fix to remove the union that was causing builder failures. The bindings were originally added in r251472, and reverted in r251473 due to the builder failures. llvm-svn: 251482
2015-10-28 03:40:04 +01:00
[orc] Add a trivial unit test to get the ball rolling I made my best guess at the Makefile, since I don't have a make build. I'm not sure if it should be valid to add an empty list of things, but it seemed the sort of degenerate case. llvm-svn: 230196
2015-02-23 01:36:25 +01:00
set(LLVM_LINK_COMPONENTS
Core
OrcJITTests: Update libdeps. llvm-svn: 251504
2015-10-28 10:37:09 +01:00
ExecutionEngine
[ORC] Add missing library dependency on IRReader.
2021-05-06 04:30:24 +02:00
IRReader
[ORC] Add JITLink dependence for ObjectLinkingLayerTest. This aims to fix the failure at https://lab.llvm.org/buildbot/#/builders/61/builds/9590.
2021-05-14 07:47:35 +02:00
JITLink
OrcJITTests: Update libdeps corresponding to r251604. llvm-svn: 251619
2015-10-29 07:40:04 +01:00
Object
[Orc] Make the makeStub function propagate argument attributes onto the call to the function body. This is necessary for correctness when lazily compiling. Also, flesh out the Orc unit test infrastructure slightly, and add a unit test for this. llvm-svn: 235347
2015-04-20 22:41:45 +02:00
OrcJIT
[ORC] Break up OrcJIT library, add Orc-RPC based remote TargetProcessControl implementation. This patch aims to improve support for out-of-process JITing using OrcV2. It introduces two new class templates, OrcRPCTargetProcessControlBase and OrcRPCTPCServer, which together implement the TargetProcessControl API by forwarding operations to an execution process via an Orc-RPC Endpoint. These utilities are used to implement out-of-process JITing from llvm-jitlink to a new llvm-jitlink-executor tool. This patch also breaks the OrcJIT library into three parts: -- OrcTargetProcess: Contains code needed by the JIT execution process. -- OrcShared: Contains code needed by the JIT execution and compiler processes -- OrcJIT: Everything else. This break-up allows JIT executor processes to link against OrcTargetProcess and OrcShared only, without having to link in all of OrcJIT. Clients executing JIT'd code in-process should start linking against OrcTargetProcess as well as OrcJIT. In the near future these changes will enable: -- Removal of the OrcRemoteTargetClient/OrcRemoteTargetServer class templates which provided similar functionality in OrcV1. -- Restoration of Chapter 5 of the Building-A-JIT tutorial series, which will serve as a simple usage example for these APIs. -- Implementation of lazy, cross-target compilation in lli's -jit-kind=orc-lazy mode.
2020-11-11 01:55:24 +01:00
OrcShared
[ORC] Add dependence of OrcJIT on OrcTargetProcess. The SelfTargetProcessControl class depends on OrcTargetProcess.
2020-11-13 07:48:27 +01:00
OrcTargetProcess
[cmake] Link in LLVMPasses due to dependency by LLVMOrcJIT; NFC Summary: rL367756 (f5c40cb) increases the dependency of LLVMOrcJIT on LLVMPasses. In particular, symbols defined in LLVMPasses that are referenced by the destructor of `PassBuilder` are now referenced by LLVMOrcJIT through `Speculation.cpp.o`. We believe that referencing symbols defined in LLVMPasses in the destructor of `PassBuilder` is valid, and that adding to the set of such symbols is legitimate. To support such cases, this patch adds LLVMPasses to the set of libraries being linked when linking in LLVMOrcJIT causes such symbols from LLVMPasses to be referenced. Reviewers: Whitney, anhtuyen, pree-jackie Reviewed By: pree-jackie Subscribers: mgorny, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D66441 llvm-svn: 369310
2019-08-20 01:12:48 +02:00
Passes
OrcJITTests: Update libdeps corresponding to r251604. llvm-svn: 251619
2015-10-29 07:40:04 +01:00
RuntimeDyld
[orc] Add a trivial unit test to get the ball rolling I made my best guess at the Makefile, since I don't have a make build. I'm not sure if it should be valid to add an empty list of things, but it seemed the sort of degenerate case. llvm-svn: 230196
2015-02-23 01:36:25 +01:00
Support
[Orc] Re-add C bindings for the Orc APIs, with a fix to remove the union that was causing builder failures. The bindings were originally added in r251472, and reverted in r251473 due to the builder failures. llvm-svn: 251482
2015-10-28 03:40:04 +01:00
native
[orc] Add a trivial unit test to get the ball rolling I made my best guess at the Makefile, since I don't have a make build. I'm not sure if it should be valid to add an empty list of things, but it seemed the sort of degenerate case. llvm-svn: 230196
2015-02-23 01:36:25 +01:00
)
add_llvm_unittest(OrcJITTests
[ORC] Re-apply r321838 again with a workaround for a bug present in the libcxx version being used on some of the green dragon builders (plus a clang-format). Workaround: AsynchronousSymbolQuery and VSO want to work with JITEvaluatedSymbols anyway, so just use them (instead of JITSymbol, which happens to tickle the bug). The libcxx bug being worked around was fixed in r276003, and there are plans to update the offending builders. llvm-svn: 322140
2018-01-10 01:09:38 +01:00
CoreAPIsTest.cpp
[ORC] Require ExecutorProcessControl when constructing an ExecutionSession. Wrapper function call and dispatch handler helpers are moved to ExecutionSession, and existing EPC-based tools are re-written to take an ExecutionSession argument instead. Requiring an ExecutorProcessControl instance simplifies existing EPC based utilities (which only need to take an ES now), and should encourage more utilities to use the EPC interface. It also simplifies process termination, since the session can automatically call ExecutorProcessControl::disconnect (previously this had to be done manually, and carefully ordered with the rest of JIT tear-down to work correctly).
2021-07-27 05:50:19 +02:00
ExecutionSessionWrapperFunctionCallsTest.cpp
[Orc] Make the makeStub function propagate argument attributes onto the call to the function body. This is necessary for correctness when lazily compiling. Also, flesh out the Orc unit test infrastructure slightly, and add a unit test for this. llvm-svn: 235347
2015-04-20 22:41:45 +02:00
IndirectionUtilsTest.cpp
[ORC] Extract and tidy up JITTargetMachineBuilder, add unit test. (1) Adds comments for the API. (2) Removes the setArch method: This is redundant: the setArchStr method on the triple should be used instead. (3) Turns EmulatedTLS on by default. This matches EngineBuilder's behavior. llvm-svn: 343423
2018-09-30 21:12:23 +02:00
JITTargetMachineBuilderTest.cpp
[ORC] Add a "lazy call-through" utility based on the same underlying trampoline implementation as lazy compile callbacks, and a "lazy re-exports" utility that builds lazy call-throughs. Lazy call-throughs are similar to lazy compile callbacks (and are based on the same underlying state saving/restoring trampolines) but resolve their targets by performing a standard ORC lookup rather than invoking a user supplied compiler callback. This allows them to inherit the thread-safety of ORC lookups while blocking only the calling thread (whereas compile callbacks also block one compile thread). Lazy re-exports provide a simple way of building lazy call-throughs. Unlike a regular re-export, a lazy re-export generates a new address (a stub entry point) that will act like the re-exported symbol when called. The first call via a lazy re-export will trigger compilation of the re-exported symbol before calling through to it. llvm-svn: 343061
2018-09-26 06:18:30 +02:00
LazyCallThroughAndReexportsTest.cpp
[ORC] Add support for adding LinkGraphs directly to ObjectLinkingLayer. This is separate from (but builds on) the support added in ec6b71df70a for emitting LinkGraphs in the context of an active materialization. This commit makes LinkGraphs a first-class data structure with features equivalent to object files within ObjectLinkingLayer.
2021-05-14 06:35:34 +02:00
ObjectLinkingLayerTest.cpp
[ORC] Reintroduce the ORC C API test. This test was removed in 51495fd285 due to broken bots. Its reintroduction is expected to trigger failures on some builders. The test has been modified to print error messages in full, which should aid in tracking these down.
2021-04-28 20:21:59 +02:00
OrcCAPITest.cpp
[Orc] Make the makeStub function propagate argument attributes onto the call to the function body. This is necessary for correctness when lazily compiling. Also, flesh out the Orc unit test infrastructure slightly, and add a unit test for this. llvm-svn: 235347
2015-04-20 22:41:45 +02:00
OrcTestCommon.cpp
[Orc] Break QueueChannel out into its own header and add a utility, createPairedQueueChannels, to simplify channel creation in the RPC unit tests. llvm-svn: 299611
2017-04-06 03:49:21 +02:00
QueueChannel.cpp
[ORC] Add support for resource tracking/removal (removable code). This patch introduces new APIs to support resource tracking and removal in Orc. It is intended as a thread-safe generalization of the removeModule concept from OrcV1. Clients can now create ResourceTracker objects (using JITDylib::createResourceTracker) to track resources for each MaterializationUnit (code, data, aliases, absolute symbols, etc.) added to the JIT. Every MaterializationUnit will be associated with a ResourceTracker, and ResourceTrackers can be re-used for multiple MaterializationUnits. Each JITDylib has a default ResourceTracker that will be used for MaterializationUnits added to that JITDylib if no ResourceTracker is explicitly specified. Two operations can be performed on ResourceTrackers: transferTo and remove. The transferTo operation transfers tracking of the resources to a different ResourceTracker object, allowing ResourceTrackers to be merged to reduce administrative overhead (the source tracker is invalidated in the process). The remove operation removes all resources associated with a ResourceTracker, including any symbols defined by MaterializationUnits associated with the tracker, and also invalidates the tracker. These operations are thread safe, and should work regardless of the the state of the MaterializationUnits. In the case of resource transfer any existing resources associated with the source tracker will be transferred to the destination tracker, and all future resources for those units will be automatically associated with the destination tracker. In the case of resource removal all already-allocated resources will be deallocated, any if any program representations associated with the tracker have not been compiled yet they will be destroyed. If any program representations are currently being compiled then they will be prevented from completing: their MaterializationResponsibility will return errors on any attempt to update the JIT state. Clients (usually Layer writers) wishing to track resources can implement the ResourceManager API to receive notifications when ResourceTrackers are transferred or removed. The MaterializationResponsibility::withResourceKeyDo method can be used to create associations between the key for a ResourceTracker and an allocated resource in a thread-safe way. RTDyldObjectLinkingLayer and ObjectLinkingLayer are updated to use the ResourceManager API to enable tracking and removal of memory allocated by the JIT linker. The new JITDylib::clear method can be used to trigger removal of every ResourceTracker associated with the JITDylib (note that this will only remove resources for the JITDylib, it does not run static destructors). This patch includes unit tests showing basic usage. A follow-up patch will update the Kaleidoscope and BuildingAJIT tutorial series to OrcV2 and will use this API to release code associated with anonymous expressions.
2020-09-11 18:50:41 +02:00
ResourceTrackerTest.cpp
[Orc] Add support for remote JITing to the ORC API. This patch adds utilities to ORC for managing a remote JIT target. It consists of: 1. A very primitive RPC system for making calls over a byte-stream. See RPCChannel.h, RPCUtils.h. 2. An RPC API defined in the above system for managing memory, looking up symbols, creating stubs, etc. on a remote target. See OrcRemoteTargetRPCAPI.h. 3. An interface for creating high-level JIT components (memory managers, callback managers, stub managers, etc.) that operate over the RPC API. See OrcRemoteTargetClient.h. 4. A helper class for building servers that can handle the RPC calls. See OrcRemoteTargetServer.h. The system is designed to work neatly with the existing ORC components and functionality. In particular, the ORC callback API (and consequently the CompileOnDemandLayer) is supported, enabling lazy compilation of remote code. Assuming this doesn't trigger any builder failures, a follow-up patch will be committed which tests these utilities by using them to replace LLI's existing remote-JITing demo code. llvm-svn: 257305
2016-01-11 02:40:11 +01:00
RPCUtilsTest.cpp
[Orc] Break QueueChannel out into its own header and add a utility, createPairedQueueChannels, to simplify channel creation in the RPC unit tests. llvm-svn: 299611
2017-04-06 03:49:21 +02:00
RTDyldObjectLinkingLayerTest.cpp
[ORC] Port WrapperFunctionUtils and SimplePackedSerialization from ORC runtime. Replace the existing WrapperFunctionResult type in llvm/include/ExecutionEngine/Orc/Shared/TargetProcessControlTypes.h with a version adapted from the ORC runtime's implementation. Also introduce the SimplePackedSerialization scheme (also adapted from the ORC runtime's implementation) for wrapper functions to avoid manual serialization and deserialization for calls to runtime functions involving common types.
2021-06-15 12:26:51 +02:00
SimplePackedSerializationTest.cpp
[Orc] Add a SymbolStringPool data structure for efficient storage and fast comparison of symbol names. SymbolStringPool is a thread-safe string pool that will be used in upcoming Orc APIs to facilitate efficient storage and fast comparison of symbol name strings. llvm-svn: 319839
2017-12-05 22:44:56 +01:00
SymbolStringPoolTest.cpp
Revert "Re-revert r343129." This reverts commit 4e2557dbc76704beb8c4cf1191cb786e719db5d3. llvm-svn: 343161
2018-09-27 04:09:36 +02:00
ThreadSafeModuleTest.cpp
[ORC] Port WrapperFunctionUtils and SimplePackedSerialization from ORC runtime. Replace the existing WrapperFunctionResult type in llvm/include/ExecutionEngine/Orc/Shared/TargetProcessControlTypes.h with a version adapted from the ORC runtime's implementation. Also introduce the SimplePackedSerialization scheme (also adapted from the ORC runtime's implementation) for wrapper functions to avoid manual serialization and deserialization for calls to runtime functions involving common types.
2021-06-15 12:26:51 +02:00
WrapperFunctionUtilsTest.cpp
[orc] Add a trivial unit test to get the ball rolling I made my best guess at the Makefile, since I don't have a make build. I'm not sure if it should be valid to add an empty list of things, but it seemed the sort of degenerate case. llvm-svn: 230196
2015-02-23 01:36:25 +01:00
)
[Orc] Add pthread dependence to the RPCUtilsTest unit test. llvm-svn: 266766
2016-04-19 19:13:52 +02:00
[ORC] Remove symbols from dependency lists when failing materialization. When failing materialization of a symbol X, remove X from the dependants list of any of X's dependencies. This ensures that when X's dependencies are emitted (or fail themselves) they do not try to access the no-longer-existing MaterializationInfo for X. llvm-svn: 359252
2019-04-26 01:31:33 +02:00
target_link_libraries(OrcJITTests PRIVATE
LLVMTestingSupport
${ORC_JIT_TEST_LIBS})
Reference in New Issue Copy Permalink