[all-commits] [llvm/llvm-project] e41ebb: [mlir][RFC] Refactor layout representation in MemR...
Vladislav Vinogradov via All-commits
all-commits at lists.llvm.org
Tue Oct 19 02:43:09 PDT 2021
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: e41ebbecf97ac70326dfa2c54e3ef5fa13df54eb
https://github.com/llvm/llvm-project/commit/e41ebbecf97ac70326dfa2c54e3ef5fa13df54eb
Author: Vladislav Vinogradov <vlad.vinogradov at intel.com>
Date: 2021-10-19 (Tue, 19 Oct 2021)
Changed paths:
M mlir/include/mlir-c/BuiltinTypes.h
M mlir/include/mlir/IR/BuiltinAttributeInterfaces.h
M mlir/include/mlir/IR/BuiltinAttributeInterfaces.td
M mlir/include/mlir/IR/BuiltinAttributes.td
M mlir/include/mlir/IR/BuiltinTypes.h
M mlir/include/mlir/IR/BuiltinTypes.td
M mlir/lib/Analysis/LoopAnalysis.cpp
M mlir/lib/Analysis/Utils.cpp
M mlir/lib/Bindings/Python/IRTypes.cpp
M mlir/lib/CAPI/IR/BuiltinTypes.cpp
M mlir/lib/Conversion/LLVMCommon/Pattern.cpp
M mlir/lib/Conversion/MemRefToLLVM/MemRefToLLVM.cpp
M mlir/lib/Conversion/VectorToLLVM/ConvertVectorToLLVM.cpp
M mlir/lib/Dialect/GPU/IR/GPUDialect.cpp
M mlir/lib/Dialect/GPU/Transforms/AllReduceLowering.cpp
M mlir/lib/Dialect/Linalg/Transforms/ComprehensiveBufferize.cpp
M mlir/lib/Dialect/Linalg/Transforms/DropUnitDims.cpp
M mlir/lib/Dialect/MemRef/IR/MemRefOps.cpp
M mlir/lib/Dialect/Vector/VectorOps.cpp
M mlir/lib/IR/AsmPrinter.cpp
M mlir/lib/IR/BuiltinAttributeInterfaces.cpp
M mlir/lib/IR/BuiltinTypes.cpp
M mlir/lib/Parser/TypeParser.cpp
M mlir/lib/Transforms/NormalizeMemRefs.cpp
M mlir/lib/Transforms/PipelineDataTransfer.cpp
M mlir/lib/Transforms/Utils/LoopUtils.cpp
M mlir/lib/Transforms/Utils/Utils.cpp
M mlir/test/CAPI/ir.c
M mlir/test/Dialect/Vector/invalid.mlir
M mlir/test/IR/invalid-ops.mlir
M mlir/test/IR/invalid.mlir
M mlir/test/IR/parser.mlir
M mlir/test/python/ir/builtin_types.py
M mlir/unittests/IR/ShapedTypeTest.cpp
Log Message:
-----------
[mlir][RFC] Refactor layout representation in MemRefType
The change is based on the proposal from the following discussion:
https://llvm.discourse.group/t/rfc-memreftype-affine-maps-list-vs-single-item/3968
* Introduce `MemRefLayoutAttr` interface to get `AffineMap` from an `Attribute`
(`AffineMapAttr` implements this interface).
* Store layout as a single generic `MemRefLayoutAttr`.
This change removes the affine map composition feature and related API.
Actually, while the `MemRefType` itself supported it, almost none of the upstream
can work with more than 1 affine map in `MemRefType`.
The introduced `MemRefLayoutAttr` allows to re-implement this feature
in a more stable way - via separate attribute class.
Also the interface allows to use different layout representations rather than affine maps.
For example, the described "stride + offset" form, which is currently supported in ASM parser only,
can now be expressed as separate attribute.
Reviewed By: ftynse, bondhugula
Differential Revision: https://reviews.llvm.org/D111553
More information about the All-commits
mailing list