llvm-mirror/unittests/ExecutionEngine/Orc/CMakeLists.txt


set(LLVM_LINK_COMPONENTS
  Core
  ExecutionEngine
  Object
  OrcJIT
  RuntimeDyld
  Support
  native
  )

add_llvm_unittest(OrcJITTests
  CompileOnDemandLayerTest.cpp
  CoreAPIsTest.cpp
  IndirectionUtilsTest.cpp
  GlobalMappingLayerTest.cpp
  LazyCallThroughAndReexportsTest.cpp
  LazyEmittingLayerTest.cpp
  LegacyAPIInteropTest.cpp
  ObjectTransformLayerTest.cpp
  OrcCAPITest.cpp
  OrcTestCommon.cpp
  QueueChannel.cpp
  RemoteObjectLayerTest.cpp
  RPCUtilsTest.cpp
  RTDyldObjectLinkingLayerTest.cpp
  RTDyldObjectLinkingLayer2Test.cpp
  SymbolStringPoolTest.cpp
  ThreadSafeModuleTest.cpp
  )

target_link_libraries(OrcJITTests PRIVATE ${ORC_JIT_TEST_LIBS})
[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`
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`
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] Make CompileOnDemandLayer::findSymbol call BaseLayer::findSymbol if no symbol definition is found in the logical dylibs. llvm-svn: 250796 2015-10-20 06:35:02 +02:00			`CompileOnDemandLayerTest.cpp`
[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] 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`
Add a global mapping layer for Orc. Adapted from a patch by Andy Somogyi. Thanks Andy! llvm-svn: 246226 2015-08-28 00:20:05 +02:00			`GlobalMappingLayerTest.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 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			`LazyEmittingLayerTest.cpp`
[ORC] Add orc::SymbolResolver, a Orc/Legacy API interop header, and an orc::SymbolResolver to JITSymbolResolver adapter. The new orc::SymbolResolver interface uses asynchronous queries for better performance. (Asynchronous queries with bulk lookup minimize RPC/IPC overhead, support parallel incoming queries, and expose more available work for distribution). Existing ORC layers will soon be updated to use the orc::SymbolResolver API rather than the legacy llvm::JITSymbolResolver API. Because RuntimeDyld still uses JITSymbolResolver, this patch also includes an adapter that wraps an orc::SymbolResolver with a JITSymbolResolver API. llvm-svn: 323073 2018-01-22 04:00:31 +01:00			`LegacyAPIInteropTest.cpp`
[ORC] Add ObjectTransformLayer Summary: This is a utility for clients that want to insert a layer that modifies each ObjectFile and then passes it along to the next layer. Reviewers: lhames Reviewed By: lhames Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D10456 llvm-svn: 240640 2015-06-25 15:35:22 +02:00			`ObjectTransformLayerTest.cpp`
[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			`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 a pair of ORC layers that forward object-layer operations via RPC. This patch introduces RemoteObjectClientLayer and RemoteObjectServerLayer, which can be used to forward ORC object-layer operations from a JIT stack in the client to a JIT stack (consisting only of object-layers) in the server. This is a new way to support remote-JITing in LLVM. The previous approach (supported by OrcRemoteTargetClient and OrcRemoteTargetServer) used a remote-mapping memory manager that sat "beneath" the JIT stack and sent fully-relocated binary blobs to the server. The main advantage of the new approach is that relocatable objects can be cached on the server and re-used (if the code that they represent hasn't changed), whereas fully-relocated blobs can not (since the addresses they have been permanently bound to will change from run to run). llvm-svn: 312511 2017-09-05 05:34:09 +02:00			`RemoteObjectLayerTest.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] Add unit tests for the new RTDyldObjectLinkingLayer2 class. The new unit tests match the old ones, which will remain in tree until the old RTDyldObjectLinkingLayer is removed. llvm-svn: 340786 2018-08-28 00:30:57 +02:00			`RTDyldObjectLinkingLayer2Test.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] 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][cmake] Check if 8 byte atomics require libatomic for unittest rL319838 introduced SymbolStringPool which uses 8 byte atomics for reference counters. On systems which do not support such atomics natively such as MIPS32, explicitly add libatomic as one of the libraries for SymbolStringPool's unittest. Reviewers: lhames, beanz Differential Revision: https://reviews.llvm.org/D41010 llvm-svn: 321225 2017-12-20 23:26:41 +01:00			`target_link_libraries(OrcJITTests PRIVATE ${ORC_JIT_TEST_LIBS})`