108b08f2a9
Static op verification cannot detect cases where an op is valid at compile time but may be invalid at runtime. An example of such an op is `memref::ExpandShapeOp`. Invalid at compile time: `memref.expand_shape %m [[0, 1]] : memref<11xf32> into memref<2x5xf32>` Valid at compile time (because we do not know any better): `memref.expand_shape %m [[0, 1]] : memref<?xf32> into memref<?x5xf32>`. This op may or may not be valid at runtime depending on the runtime shape of `%m`. Invalid runtime ops such as the one above are hard to debug because they can crash the program execution at a seemingly unrelated position or (even worse) compute an invalid result without crashing. This revision adds a new op interface `RuntimeVerifiableOpInterface` that can be implemented by ops that provide additional runtime verification. Such runtime verification can be computationally expensive, so it is only generated on an opt-in basis by running `-generate-runtime-verification`. A simple runtime verifier for `memref::ExpandShapeOp` is provided as an example. Differential Revision: https://reviews.llvm.org/D138576
33 lines
626 B
CMake
33 lines
626 B
CMake
add_mlir_dialect_library(MLIRMemRefTransforms
|
|
ComposeSubView.cpp
|
|
ExpandOps.cpp
|
|
ExpandStridedMetadata.cpp
|
|
EmulateWideInt.cpp
|
|
FoldMemRefAliasOps.cpp
|
|
MultiBuffer.cpp
|
|
NormalizeMemRefs.cpp
|
|
ResolveShapedTypeResultDims.cpp
|
|
RuntimeOpVerification.cpp
|
|
|
|
ADDITIONAL_HEADER_DIRS
|
|
${MLIR_MAIN_INCLUDE_DIR}/mlir/Dialect/MemRef
|
|
|
|
DEPENDS
|
|
MLIRMemRefPassIncGen
|
|
|
|
LINK_LIBS PUBLIC
|
|
MLIRAffineDialect
|
|
MLIRAffineUtils
|
|
MLIRArithDialect
|
|
MLIRArithTransforms
|
|
MLIRFuncDialect
|
|
MLIRInferTypeOpInterface
|
|
MLIRLoopLikeInterface
|
|
MLIRMemRefDialect
|
|
MLIRPass
|
|
MLIRTensorDialect
|
|
MLIRTransforms
|
|
MLIRVectorDialect
|
|
)
|
|
|