Canonicalize affine set + operands in addAffineIfOpDomain. This is to
ensure a unique set of operands for FlatAffineValueConstraints and in
general to provide a simplified set of constraints. For the latter
scenario, this just leads to efficiency improvements as opposed to
functionality.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/test/Transforms/memref-dependence-check.mlir | ||
---|---|---|
1090 | Do we need to call multiple affine.store to reproduce the situation originally reported? |
mlir/test/Transforms/memref-dependence-check.mlir | ||
---|---|---|
1090 | Not for dependence checking. To test this change, a single store is sufficient when exercised from dependence analysis. It's the load in the empty set that's key. For scalrep, yes, dependence analysis is triggered when you have multiple stores - to check whether the second store intervenes. |
Do we need to call multiple affine.store to reproduce the situation originally reported?