separate AffineMapAccessInterface from AffineRead/WriteOpInterface
authorAdam Straw <26910851+adstraw@users.noreply.github.com>
Tue, 16 Feb 2021 21:03:03 +0000 (13:03 -0800)
committerJeremy Bruestle <jeremy.bruestle@intel.com>
Tue, 16 Feb 2021 21:05:27 +0000 (13:05 -0800)
commit99c0458f2f53ec26d663e5b9ad750e54ecf51d4b
tree48158c405775980d198ce2cf5d3188d5295fa3a4
parent5aa8f4c0843a68a24cb37dce5c0248c849d7d476
separate AffineMapAccessInterface from AffineRead/WriteOpInterface

Separating the AffineMapAccessInterface from AffineRead/WriteOp interface so that dialects which extend Affine capabilities (e.g. PlaidML PXA = parallel extensions for Affine) can utilize relevant passes (e.g. MemRef normalization).

Reviewed By: bondhugula

Differential Revision: https://reviews.llvm.org/D96284
mlir/include/mlir/Dialect/Affine/IR/AffineMemoryOpInterfaces.td
mlir/include/mlir/Dialect/Affine/IR/AffineOps.h
mlir/include/mlir/Dialect/Affine/IR/AffineOps.td
mlir/lib/Dialect/Affine/Transforms/AffineLoopInvariantCodeMotion.cpp
mlir/lib/Transforms/LoopFusion.cpp
mlir/lib/Transforms/Utils/Utils.cpp