Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
This CL looks incomplete, since you're not actually using isSameTypesWithoutEncoding anywhere...
mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensor.h | ||
---|---|---|
105 ↗ | (On Diff #518065) | Should be just "Type" not "Types" |
mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensor.h | ||
---|---|---|
105 ↗ | (On Diff #518065) | hrmm, it looks like that's the name used by lib/Dialect/Tensor/IR/TensorOps.cpp... So I guess consistency is probably better than grammatical correctness... |
mlir/include/mlir/Dialect/SparseTensor/IR/SparseTensor.h | ||
---|---|---|
105 ↗ | (On Diff #518065) | Actually, now that I've seen that other version of this function, I think it would be better to have this CL change the lib/Dialect/Tensor/IR/TensorOps.cpp version from being static to being exported via include/Dialect/Tensor/IR/TensorOps.h. And then you should use that public version for whatever you needed here |
mlir/lib/Dialect/SparseTensor/Transforms/SparseTensorRewriting.cpp | ||
---|---|---|
378 | We actually wanted to add this to verify() proper (and fully reject such cases). But there was also some push back with adding sparse specific checks in tensor dialect. This walks a bit of a middle ground until we come up with a full design that everybody likes followed by full audit of "dense" code. |
mlir/lib/Dialect/Tensor/IR/TensorOps.cpp | ||
---|---|---|
113 | I am usually all +1 on minimizing diffs. But here the original static method was in a section marked " Reassociative reshape ops" so I decided to move it up (where the other public methods are defined, and in same order as header file). |
The non-sparse part looks good to me! I'll leave the final approval to @wrengr. Thanks!
mlir/lib/Dialect/SparseTensor/Transforms/SparseTensorRewriting.cpp | ||
---|---|---|
378 | I'm fine with leaving this rewriting case here, I was just wondering whether MLIR had some way to emit warnings despite also returning success. That is, since we consider this rewrite to be dubious, it'd be nice to give users some sort of notification whenever it fires. (perhaps only doing so whenever they set the debugging verbosity high enough) |
mlir/lib/Dialect/SparseTensor/Transforms/SparseTensorRewriting.cpp | ||
---|---|---|
378 | For sure, I don't believe we have any good precedent for that at the moment. If we get this, we may add it here (or, hopefully one day, just reject the op in dense verify() case ;-) |
I would use "when" here rather than "but"