llvm-project/llvm/lib/ExecutionEngine/Orc/CMakeLists.txt

add_llvm_library(LLVMOrcJIT
  CompileOnDemandLayer.cpp
  Core.cpp
  ExecutionUtils.cpp
  IndirectionUtils.cpp
  IRCompileLayer.cpp
  IRTransformLayer.cpp
  LazyReexports.cpp
  Legacy.cpp
  Layer.cpp
  LLJIT.cpp
  NullResolver.cpp
  ObjectTransformLayer.cpp
  OrcABISupport.cpp
  OrcCBindings.cpp
  OrcError.cpp
  OrcMCJITReplacement.cpp
  RPCUtils.cpp
  RTDyldObjectLinkingLayer.cpp
  ThreadSafeModule.cpp

  ADDITIONAL_HEADER_DIRS
  ${LLVM_MAIN_INCLUDE_DIR}/llvm/ExecutionEngine/Orc

  DEPENDS
  intrinsics_gen
  )

target_link_libraries(LLVMOrcJIT
  PRIVATE
  LLVMBitReader
  LLVMBitWriter
  )
Fix line endings (NFC) I inadvertently checked these in with Windows-style line endings in r240288. llvm-svn: 240340 2015-06-23 05:37:34 +08:00			`add_llvm_library(LLVMOrcJIT`
[ORC] Add an initial implementation of a replacement CompileOnDemandLayer. CompileOnDemandLayer2 is a replacement for CompileOnDemandLayer built on the ORC Core APIs. Functions in added modules are extracted and compiled lazily. CompileOnDemandLayer2 supports multithreaded JIT'd code, and compilation on multiple threads. llvm-svn: 334967 2018-06-19 02:01:43 +08:00			`CompileOnDemandLayer.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 08:09:38 +08:00			`Core.cpp`
Fix line endings (NFC) I inadvertently checked these in with Windows-style line endings in r240288. llvm-svn: 240340 2015-06-23 05:37:34 +08:00			`ExecutionUtils.cpp`
			`IndirectionUtils.cpp`
[LKH] Add a new IRCompileLayer. llvm-svn: 333127 2018-05-24 05:27:01 +08:00			`IRCompileLayer.cpp`
[LKH] Add a new IRTransformLayer. llvm-svn: 333129 2018-05-24 05:27:07 +08:00			`IRTransformLayer.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 12:18:30 +08:00			`LazyReexports.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 11:00:31 +08:00			`Legacy.cpp`
[ORC] Add IRLayer and ObjectLayer interfaces and related MaterializationUnits. llvm-svn: 332896 2018-05-22 05:11:13 +08:00			`Layer.cpp`
[ORC] Add LLJIT and LLLazyJIT, and replace OrcLazyJIT in LLI with LLLazyJIT. LLJIT is a prefabricated ORC based JIT class that is meant to be the go-to replacement for MCJIT. Unlike OrcMCJITReplacement (which will continue to be supported) it is not API or bug-for-bug compatible, but targets the same use cases: Simple, non-lazy compilation and execution of LLVM IR. LLLazyJIT extends LLJIT with support for function-at-a-time lazy compilation, similar to what was provided by LLVM's original (now long deprecated) JIT APIs. This commit also contains some simple utility classes (CtorDtorRunner2, LocalCXXRuntimeOverrides2, JITTargetMachineBuilder) to support LLJIT and LLLazyJIT. Both of these classes are works in progress. Feedback from JIT clients is very welcome! llvm-svn: 335670 2018-06-27 05:35:48 +08:00			`LLJIT.cpp`
Fix line endings (NFC) I inadvertently checked these in with Windows-style line endings in r240288. llvm-svn: 240340 2015-06-23 05:37:34 +08:00			`NullResolver.cpp`
[LKH] Add ObjectTransformLayer2. llvm-svn: 333128 2018-05-24 05:27:06 +08:00			`ObjectTransformLayer.cpp`
[Orc] Rename OrcArchitectureSupport to OrcABISupport and add Win32 ABI support. This enables lazy JITing on Windows x86-64. Patch by David. Thanks David! llvm-svn: 268845 2016-05-07 11:36:38 +08:00			`OrcABISupport.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 10:40:04 +08:00			`OrcCBindings.cpp`
[Orc] Add error codes and a new std::error_category for remote-jit errors. These will be used by an upcoming patch that adds remote-jit support utilities to ORC. llvm-svn: 257297 2016-01-11 08:34:13 +08:00			`OrcError.cpp`
Fix line endings (NFC) I inadvertently checked these in with Windows-style line endings in r240288. llvm-svn: 240340 2015-06-23 05:37:34 +08:00			`OrcMCJITReplacement.cpp`
[ORC] Use native Errors rather than converted std::error_codes for ORC RPC. llvm-svn: 300155 2017-04-13 09:03:06 +08:00			`RPCUtils.cpp`
[LKH] Add a replacement RTDyldLayer. llvm-svn: 332918 2018-05-22 07:45:40 +08:00			`RTDyldObjectLinkingLayer.cpp`
[ORC] Add ThreadSafeModule and ThreadSafeContext wrappers to support concurrent compilation of IR in the JIT. ThreadSafeContext is a pair of an LLVMContext and a mutex that can be used to lock that context when it needs to be accessed from multiple threads. ThreadSafeModule is a pair of a unique_ptr<Module> and a shared_ptr<ThreadSafeContext>. This allows the lifetime of a ThreadSafeContext to be managed automatically in terms of the ThreadSafeModules that refer to it: Once all modules using a ThreadSafeContext are destructed, and providing the client has not held on to a copy of shared context pointer, the context will be automatically destructed. This scheme is necessary due to the following constraits: (1) We need multiple contexts for multithreaded compilation (at least one per compile thread plus one to store any IR not currently being compiled, though one context per module is simpler). (2) We need to free contexts that are no longer being used so that the JIT does not leak memory over time. (3) Module lifetimes are not predictable (modules are compiled as needed depending on the flow of JIT'd code) so there is no single point where contexts could be reclaimed. JIT clients not using concurrency can safely use one ThreadSafeContext for all ThreadSafeModules. JIT clients who want to be able to compile concurrently should use a different ThreadSafeContext for each module, or call setCloneToNewContextOnEmit on their top-level IRLayer. The former reduces compile latency (since no clone step is needed) at the cost of additional memory overhead for uncompiled modules (as every uncompiled module will duplicate the LLVM types, constants and metadata that have been shared). llvm-svn: 343055 2018-09-26 09:24:12 +08:00			`ThreadSafeModule.cpp`
Fix line endings (NFC) I inadvertently checked these in with Windows-style line endings in r240288. llvm-svn: 240340 2015-06-23 05:37:34 +08:00
			`ADDITIONAL_HEADER_DIRS`
			`${LLVM_MAIN_INCLUDE_DIR}/llvm/ExecutionEngine/Orc`

			`DEPENDS`
			`intrinsics_gen`
			`)`
[ORC] Add BitReader/BitWriter to target_link_libraries Summary: CompileOnDemandLayer.cpp uses function in these libraries, and builds with `-DSHARED_LIB=ON` fail without this. Reviewers: lhames Subscribers: mgorny, llvm-commits Differential Revision: https://reviews.llvm.org/D48995 llvm-svn: 336389 2018-07-06 05:23:15 +08:00
			`target_link_libraries(LLVMOrcJIT`
			`PRIVATE`
			`LLVMBitReader`
			`LLVMBitWriter`
			`)`