These properties were useful for a few things before traits had a better integration story, but don't really carry their weight well these days. Most of these properties are already checked via traits in most of the code. It is better to align the system around traits, and improve the performance/cost of traits in general.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/lib/Dialect/Affine/IR/AffineOps.cpp | ||
---|---|---|
391 | Alternatively a helper function may make this nicer to read !isKnownIsolatedFromAbove(region->getParentOp()) and it just simply queries the trait. |
Comment Actions
Nice. Looks good. I assume you checked this doesn't regress anything significantly in practice?
mlir/include/mlir/IR/Operation.h | ||
---|---|---|
485 | nit: absOp makes me think of mathematical abs. spell out abstractOp |
Comment Actions
Yeah, for the benchmarks I was running there was no visible change in execution outside of noise.
mlir/lib/Dialect/Affine/IR/AffineOps.cpp | ||
---|---|---|
391 | I'd prefer to keep this consistent with other traits for now. |
nit: absOp makes me think of mathematical abs. spell out abstractOp