llvm-project/mlir/lib/Pass/CMakeLists.txt

add_mlir_library(MLIRPass
  IRPrinting.cpp
  Pass.cpp
  PassCrashRecovery.cpp
  PassManagerOptions.cpp
  PassRegistry.cpp
  PassStatistics.cpp
  PassTiming.cpp

  ADDITIONAL_HEADER_DIRS
  ${MLIR_MAIN_INCLUDE_DIR}/mlir/Pass

  DEPENDS
  mlir-generic-headers

  LINK_LIBS PUBLIC
  MLIRAnalysis
  MLIRIR
  )
[MLIR] Add support for libMLIR.so Putting this up mainly for discussion on how this should be done. I am interested in MLIR from the Julia side and we currently have a strong preference to dynamically linking against the LLVM shared library, and would like to have a MLIR shared library. This patch adds a new cmake function add_mlir_library() which accumulates a list of targets to be compiled into libMLIR.so. Note that not all libraries make sense to be compiled into libMLIR.so. In particular, we want to avoid libraries which primarily exist to support certain tools (such as mlir-opt and mlir-cpu-runner). Note that the resulting libMLIR.so depends on LLVM, but does not contain any LLVM components. As a result, it is necessary to link with libLLVM.so to avoid linkage errors. So, libMLIR.so requires LLVM_BUILD_LLVM_DYLIB=on FYI, Currently it appears that LLVM_LINK_LLVM_DYLIB is broken because mlir-tblgen is linked against libLLVM.so and and independent LLVM components. Previous version of this patch broke depencies on TableGen targets. This appears to be because it compiled all libraries to OBJECT libraries (probably because cmake is generating different target names). Avoiding object libraries results in correct dependencies. (updated by Stephen Neuendorffer) Differential Revision: https://reviews.llvm.org/D73130 2020-02-09 11:27:54 +08:00			`add_mlir_library(MLIRPass`
[MLIR][cmake] don't glob for sources. Generally speaking, this is bad practice. It also causes the build to break if there are editor temporary files. Differential Revision: https://reviews.llvm.org/D79906 2020-05-14 04:40:06 +08:00			`IRPrinting.cpp`
			`Pass.cpp`
[mlir] Refactor the implementation of pass crash reproducers The current implementation has several key limitations and weirdness, e.g local reproducers don't support dynamic pass pipelines, error messages don't include the passes that failed, etc. This revision refactors the implementation to support more use cases, and also be much cleaner. The main change in this revision, aside from moving the implementation out of Pass.cpp and into its own file, is the addition of a crash recovery pass instrumentation. For local reproducers, this instrumentation handles setting up the recovery context before executing each pass. For global reproducers, the instrumentation is used to provide a more detailed error message, containing information about which passes are running and on which operations. Example of new message: ``` error: Failures have been detected while processing an MLIR pass pipeline note: Pipeline failed while executing [`TestCrashRecoveryPass` on 'module' operation: @foo]: reproducer generated at `crash-recovery.mlir.tmp` ``` Differential Revision: https://reviews.llvm.org/D101854 2021-05-20 07:53:35 +08:00			`PassCrashRecovery.cpp`
[MLIR][cmake] don't glob for sources. Generally speaking, this is bad practice. It also causes the build to break if there are editor temporary files. Differential Revision: https://reviews.llvm.org/D79906 2020-05-14 04:40:06 +08:00			`PassManagerOptions.cpp`
			`PassRegistry.cpp`
			`PassStatistics.cpp`
			`PassTiming.cpp`
Add build files and update README. * Add initial version of build files; * Update README with instructions to download and build MLIR from github; -- PiperOrigin-RevId: 241102092 2019-03-30 13:10:12 +08:00
			`ADDITIONAL_HEADER_DIRS`
			`${MLIR_MAIN_INCLUDE_DIR}/mlir/Pass`
[MLIR] Reapply: Adjust libMLIR building to more closely follow libClang This reverts commit ab1ca6e60fc58b857cc5030ca6e024d20d919cb9. 2020-05-05 03:41:43 +08:00
			`DEPENDS`
			`mlir-generic-headers`

			`LINK_LIBS PUBLIC`
[MLIR] Ensure that target_link_libraries() always has a keyword. CMake allows calling target_link_libraries() without a keyword, but this usage is not preferred when also called with a keyword, and has surprising behavior. This patch explicitly specifies a keyword when using target_link_libraries(). Differential Revision: https://reviews.llvm.org/D75725 2020-03-06 03:49:42 +08:00			`MLIRAnalysis`
			`MLIRIR`
[MLIR] Reapply: Adjust libMLIR building to more closely follow libClang This reverts commit ab1ca6e60fc58b857cc5030ca6e024d20d919cb9. 2020-05-05 03:41:43 +08:00			`)`