This addressed some unresolved comments in https://reviews.llvm.org/D142930
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.h | ||
---|---|---|
46 | I think it'd be better to define using TensorLevel = unsigned; and compress things like we do for TensorLoopId. | |
241 | I think you should just define the struct directly, rather than using std::tuple. That way client code can use nice names for accessing the fields directly, rather than defining all those wrappers around std::get<N>. Also, the struct should be named LoopSliceInfo for consistency with LoopInfo, SliceInfo, etc. And, of course, the struct should be final. If you are concerned about the ability to use structured-binding in the foreach-loops, then take a look at the "Case 3: binding to data members" section of https://en.cppreference.com/w/cpp/language/structured_binding . tl;dr: the syntax/semantics should be exactly the same as for the std::tuple case. | |
255 | I think the name tidLvls would be a lot cleaner here, and consistent with elsewhere. | |
260–263 | I think it'd be best to leave this as "operating on" like it was before. Although this is "iterating" in the sparse-compiler sense of enumerating the stored values of sparse-tensors, I feel that using that term here would cause confusion vs the C++ iterator framework | |
262 | Grammatically, that should be "information" (singular, and lowercase). However, I think it'd be better to leave it as "slice-driven loop conditions" like it was before, since the term "information" doesn't really tell us very much about what exactly that means/contains. | |
mlir/lib/Dialect/SparseTensor/Transforms/SparseTensorRewriting.cpp | ||
954–956 | Why keep this defn of ld around but commented out? If it's no longer needed, then should remove it (along with my fixme comment about trying to figure out what it's actually supposed to be) | |
mlir/lib/Dialect/SparseTensor/Transforms/Sparsification.cpp | ||
1304–1308 | should be "tidLvl" to match the names used elsewhere | |
1305 | It seems worth adding a comment explaining why we discard tlPair.second and use ldx instead; i.e., a comment saying that isSparse is checking whether any tensor is sparse for the loop ldx, regardless of what level that corresponds to and regardless of what level is stored in tidLvls. (Or, if the levels in tidLvls are supposed to agree with the loop, then say that instead. Assuming we actually maintain that invariant, then we don't need to add assertions to verify that; but we do want a comment explaining that this invariant holds.) | |
1552 | Why condTidLvls instead of just tidLvls? (I'm not saying it should be changed, just curious why the different name) | |
1652 | I think the affineTidLvls and affines should actually be combined into a single SmallVector<TLA> where struct TLA final { TensorId; Level; AffineExpr } (or struct TLA final {TensorLevel; AffineExpr} with the appropriate getters). That helps capture the invariant that translateBitsToTidLvlPairs keeps the the same length, and thus also helps avoid needing to zip them together later on Of course, you'll need to come up with a better name than my "TLA" ;) |
mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.h | ||
---|---|---|
241 | Actually I delete the wrappers, I find them useless. We only use in in structure-bindings in foreach loop, and this is a private type so it should be okay? WDYT? |
mlir/lib/Dialect/SparseTensor/Transforms/Sparsification.cpp | ||
---|---|---|
1552 | Because the callsites was using condTid (to distinguish from affineTid). but yeah, cond- is not a accurate prefix, since not all tid, lvl are appeared in the loop condition (most of the dense levels are not). I changed it to tidLvls |
mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.h | ||
---|---|---|
241 | I still think we should define our own struct rather than reusing std::tuple. I feel like the std::pair/std::tuple classes are really only intended to be used for those cases where folks need an ad-hoc struct; hence, whenever things aren't ad-hoc then they should be given their own definitions. |
mlir/lib/Dialect/SparseTensor/Transforms/Sparsification.cpp | ||
---|---|---|
1652 | I want to keep it, because the affineTidLvls are used independently from affines later. See L1662 |
mlir/lib/Dialect/SparseTensor/Transforms/CodegenEnv.h | ||
---|---|---|
92 | This should be TensorId | |
92 | This should be Level | |
mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.cpp | ||
764 | It's more appropriate to use push_back here, since the return type of makeTensorLevel is exactly what's being stored (i.e., it's not being passed to some constructor for what's actually stored) | |
770 | ditto, should be push_back | |
mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.h | ||
203 | I think a name like unpackTensorLevel would better match makeTensorLevel. | |
208 | This should use "///" since it's documentation not a comment | |
208 | I get what you're after by saying "Container<>" and "range<>", however since those are not actual names of templates, it'd be better to rephrase this to "Converts a range of TensorLevel to a range of std::pair<TensorId, Level>." | |
210 | I think you'll want to add std::remove_const_t there too, since that's what all the analogous sfinae code in MLIR does for this sort of thing. | |
214 | Mirroring the earlier suggestion, this would then be unpackTensorLevelRange | |
216 | this should be std::forward<ContainerTy>(c) | |
241 | Should be final. | |
242–244 | style-guide says that the fields should be at the end of the defn | |
260–263 | Should be just "tensor" | |
mlir/lib/Dialect/SparseTensor/Transforms/Sparsification.cpp | ||
1495 | push_back | |
1564 | push_back | |
1582 | push_back | |
1585 | push_back | |
1622–1623 | push_back | |
1634 | push_back | |
1659–1660 | I still think it'd be better to have a single SmallVector<std::pair<TensorLevel, AffineExpr>> since that helps capture the invariant that these should be the same length. But if you're not going to do that, then you should use llvm::zip_equal so that it checks that they have the same length rather than silently truncating things to the shorter list | |
1666–1668 | If this concat is what's making you reluctant to use SmallVector<std::pair<TensorLevel, AffineExpr>>, then recall that you can use llvm::concat<TensorLevel>(tidLvls, llvm::make_first_range(affineTidLvlExprs)). |
mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.h | ||
---|---|---|
210 | it should be in the order remove_reference_t<remove_const_t<, at least that's the order I see elsewhere, haven't checked to see if/how it matters |
mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.h | ||
---|---|---|
210 | I don't think it matters, but yeah, good to be consistent anyway. |
mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.h | ||
---|---|---|
210 | For the record, the order matters https://stackoverflow.com/questions/30690269/why-does-using-stdremove-reference-and-stdremove-const-in-different-order-pr |
@Peiming can you please check, the build is failing. Pasting the link to premerge-check https://buildkite.com/llvm-project/premerge-checks/builds/150384#0187e78d-a047-440e-9018-0eecabff91c8
In file included from /home/scratch/llvm-project/mlir/lib/Dialect/SparseTensor/Transforms/CodegenEnv.h:17, from /home/scratch/llvm-project/mlir/lib/Dialect/SparseTensor/Transforms/Sparsification.cpp:13: /home/scratch/llvm-project/mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.h: In member function ‘constexpr mlir::sparse_tensor::TensorLevel mlir::sparse_tensor::LoopEmitter::makeTensorLevel(mlir::sparse_tensor::TensorId, mlir::sparse_tensor::Level) const’: /home/scratch/llvm-project/mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.h:199:29: error: call to non-‘constexpr’ function ‘unsigned int mlir::sparse_tensor::LoopEmitter::getNumTensors() const’ 199 | return l * getNumTensors() + t; | ~~~~~~~~~~~~~^~ /home/scratch/llvm-project/mlir/lib/Dialect/SparseTensor/Transforms/LoopEmitter.h:195:12: note: ‘unsigned int mlir::sparse_tensor::LoopEmitter::getNumTensors() const’ declared here 195 | unsigned getNumTensors() const { return tensors.size(); } | ^~~~~~~~~~~~~ In file included from /usr/include/c++/11/cassert:44, from /home/scratch/llvm-project/llvm/include/llvm/Support/CommandLine.h:34, from /home/scratch/llvm-project/mlir/include/mlir/Pass/PassOptions.h:21, from /home/scratch/llvm-project/mlir/include/mlir/Pass/PassRegistry.h:17, from /home/scratch/llvm-project/mlir/include/mlir/Pass/Pass.h:13, from /home/scratch/llvm-project/mlir/include/mlir/Dialect/SparseTensor/Transforms/Passes.h:21, from /home/scratch/llvm-project/mlir/lib/Dialect/SparseTensor/Transforms/CodegenEnv.h:21, from /home/scratch/llvm-project/mlir/lib/Dialect/SparseTensor/Transforms/Sparsification.cpp:13: /home/scratch/llvm-project/mlir/lib/Dialect/SparseTensor/Transforms/CodegenEnv.h: In member function ‘constexpr mlir::sparse_tensor::TensorLevel mlir::sparse_tensor::CodegenEnv::makeTensorLevel(mlir::sparse_tensor::TensorId, mlir::sparse_tensor::Level) const’: /home/scratch/llvm-project/mlir/lib/Dialect/SparseTensor/Transforms/CodegenEnv.h:95:37: error: call to non-‘constexpr’ function ‘unsigned int mlir::sparse_tensor::LoopEmitter::getNumTensors() const’ 95 | assert(loopEmitter.getNumTensors() == linalgOp->getNumOperands() && | ~~~~~~~~~~~~~~~~~~~~~~~~~^~ In file included from /home/scratch/llvm-project/mlir/lib/Dialect/SparseTensor/Transforms/CodegenEnv.h:17
mlir/lib/Dialect/SparseTensor/Transforms/CodegenEnv.h | ||
---|---|---|
92 | getNumTensors cannot be called from constexpr function. |
please put this empty line back, all
Section
//
comments have whitespace around them