maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/mlir/test/lib/Transforms/CMakeLists.txt

26 lines
650 B
CMake
Raw Normal View History

Split test-specific passes out of mlir-opt Instead put their impl in test/lib and link them into mlir-test-opt PiperOrigin-RevId: 254837439
2019-06-25 05:35:21 +08:00
add_llvm_library(MLIRTestTransforms
Add initial callgraph support. Using the two call interfaces, CallOpInterface and CallableOpInterface, this change adds support for an initial multi-level CallGraph. This call graph builds a set of nodes for each callable region, and connects them via edges. An edge may be any of the following types: * Abstract - An edge not produced by a call operation, used for connecting to internal nodes from external nodes. * Call - A call edge is an edge defined via a call-like operation. * Child - This is an artificial edge connecting nested callgraph nodes. This callgraph will be used, and improved upon, to begin supporting more interesting interprocedural analyses and transformation. In a followup, this callgraph will be used to support more complex inlining support. PiperOrigin-RevId: 270724968
2019-09-24 02:43:43 +08:00
TestCallGraph.cpp
Split test-specific passes out of mlir-opt Instead put their impl in test/lib and link them into mlir-test-opt PiperOrigin-RevId: 254837439
2019-06-25 05:35:21 +08:00
TestConstantFold.cpp
TestLoopFusion.cpp
Add the initial inlining infrastructure. This defines a set of initial utilities for inlining a region(or a FuncOp), and defines a simple inliner pass for testing purposes. A new dialect interface is defined, DialectInlinerInterface, that allows for dialects to override hooks controlling inlining legality. The interface currently provides the following hooks, but these are just premilinary and should be changed/added to/modified as necessary: * isLegalToInline - Determine if a region can be inlined into one of this dialect, *or* if an operation of this dialect can be inlined into a given region. * shouldAnalyzeRecursively - Determine if an operation with regions should be analyzed recursively for legality. This allows for child operations to be closed off from the legality checks for operations like lambdas. * handleTerminator - Process a terminator that has been inlined. This cl adds support for inlining StandardOps, but other dialects will be added in followups as necessary. PiperOrigin-RevId: 267426759
2019-09-06 03:23:45 +08:00
TestInlining.cpp
Utility function to map a loop on a parametric grid of virtual processors This CL introduces a simple loop utility function which rewrites the bounds and step of a loop so as to become mappable on a regular grid of processors whose identifiers are given by SSA values. A corresponding unit test is added. For example, using CUDA terminology, and assuming a 2-d grid with processorIds = [blockIdx.x, threadIdx.x] and numProcessors = [gridDim.x, blockDim.x], the loop: ``` loop.for %i = %lb to %ub step %step { ... } ``` is rewritten into a version resembling the following pseudo-IR: ``` loop.for %i = %lb + threadIdx.x + blockIdx.x * blockDim.x to %ub step %gridDim.x * blockDim.x { ... } ``` PiperOrigin-RevId: 258945942
2019-07-19 19:47:27 +08:00
TestLoopMapping.cpp
Refactor LoopParametricTiling as a test pass - NFC This CL moves LoopParametricTiling into test/lib as a pass for purely testing purposes. PiperOrigin-RevId: 259300264
2019-07-22 19:30:50 +08:00
TestLoopParametricTiling.cpp
Fix CMake build after adding TestOpaqueLoc.cpp PiperOrigin-RevId: 273296399
2019-10-07 23:25:24 +08:00
TestOpaqueLoc.cpp
Fix public build TestMemRefStrideCalculation.cpp was missing PiperOrigin-RevId: 270304543
2019-09-21 01:49:38 +08:00
TestMemRefStrideCalculation.cpp
Split test-specific passes out of mlir-opt Instead put their impl in test/lib and link them into mlir-test-opt PiperOrigin-RevId: 254837439
2019-06-25 05:35:21 +08:00
TestVectorizationUtils.cpp
ADDITIONAL_HEADER_DIRS
${MLIR_MAIN_INCLUDE_DIR}/mlir/Transforms
)
Add the initial inlining infrastructure. This defines a set of initial utilities for inlining a region(or a FuncOp), and defines a simple inliner pass for testing purposes. A new dialect interface is defined, DialectInlinerInterface, that allows for dialects to override hooks controlling inlining legality. The interface currently provides the following hooks, but these are just premilinary and should be changed/added to/modified as necessary: * isLegalToInline - Determine if a region can be inlined into one of this dialect, *or* if an operation of this dialect can be inlined into a given region. * shouldAnalyzeRecursively - Determine if an operation with regions should be analyzed recursively for legality. This allows for child operations to be closed off from the legality checks for operations like lambdas. * handleTerminator - Process a terminator that has been inlined. This cl adds support for inlining StandardOps, but other dialects will be added in followups as necessary. PiperOrigin-RevId: 267426759
2019-09-06 03:23:45 +08:00
include_directories(${CMAKE_CURRENT_SOURCE_DIR}/../TestDialect)
include_directories(${CMAKE_CURRENT_BINARY_DIR}/../TestDialect)
Split test-specific passes out of mlir-opt Instead put their impl in test/lib and link them into mlir-test-opt PiperOrigin-RevId: 254837439
2019-06-25 05:35:21 +08:00
add_dependencies(MLIRTestTransforms MLIRStandardOpsIncGen)
target_link_libraries(MLIRTestTransforms
MLIRAffineOps
MLIRAnalysis
Utility function to map a loop on a parametric grid of virtual processors This CL introduces a simple loop utility function which rewrites the bounds and step of a loop so as to become mappable on a regular grid of processors whose identifiers are given by SSA values. A corresponding unit test is added. For example, using CUDA terminology, and assuming a 2-d grid with processorIds = [blockIdx.x, threadIdx.x] and numProcessors = [gridDim.x, blockDim.x], the loop: ``` loop.for %i = %lb to %ub step %step { ... } ``` is rewritten into a version resembling the following pseudo-IR: ``` loop.for %i = %lb + threadIdx.x + blockIdx.x * blockDim.x to %ub step %gridDim.x * blockDim.x { ... } ``` PiperOrigin-RevId: 258945942
2019-07-19 19:47:27 +08:00
MLIRLoopOps
Split test-specific passes out of mlir-opt Instead put their impl in test/lib and link them into mlir-test-opt PiperOrigin-RevId: 254837439
2019-06-25 05:35:21 +08:00
MLIRPass
Add the initial inlining infrastructure. This defines a set of initial utilities for inlining a region(or a FuncOp), and defines a simple inliner pass for testing purposes. A new dialect interface is defined, DialectInlinerInterface, that allows for dialects to override hooks controlling inlining legality. The interface currently provides the following hooks, but these are just premilinary and should be changed/added to/modified as necessary: * isLegalToInline - Determine if a region can be inlined into one of this dialect, *or* if an operation of this dialect can be inlined into a given region. * shouldAnalyzeRecursively - Determine if an operation with regions should be analyzed recursively for legality. This allows for child operations to be closed off from the legality checks for operations like lambdas. * handleTerminator - Process a terminator that has been inlined. This cl adds support for inlining StandardOps, but other dialects will be added in followups as necessary. PiperOrigin-RevId: 267426759
2019-09-06 03:23:45 +08:00
MLIRTestDialect
Split test-specific passes out of mlir-opt Instead put their impl in test/lib and link them into mlir-test-opt PiperOrigin-RevId: 254837439
2019-06-25 05:35:21 +08:00
MLIRVectorOps
)