This is to prepare for implementing a hybrid quick sort, which switches to heap
sort when the recursive depth exceeds certain limits.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/lib/Dialect/SparseTensor/Transforms/SparseBufferRewriting.cpp | ||
---|---|---|
254 | I find this a very distracting idiom to force use of an otherwise unused parameter. Is there no better way to achieve this? |
mlir/lib/Dialect/SparseTensor/Transforms/CodegenUtils.h | ||
---|---|---|
284 | not really used in this revision? |
mlir/lib/Dialect/SparseTensor/Transforms/SparseBufferRewriting.cpp | ||
---|---|---|
254 | Assuming the issue here is warnings about unused variables, then iirc you should be able to rephrase the prototype to (..., uint32_t = 0) —i.e., simply drop the name of the variable. If there are more complicated problems at hand, then I'm thinking you should rephrase the typedef to something like template <typename ...Args> using FuncGeneratorType = function_ref<void(blah blah blah, Args&&...)>; so that this particular function instantiates that template at the empty Args |
Removed irrelevant changes.
mlir/lib/Dialect/SparseTensor/Transforms/CodegenUtils.h | ||
---|---|---|
284 | Reversed this change. | |
mlir/lib/Dialect/SparseTensor/Transforms/SparseBufferRewriting.cpp | ||
254 | Please refer to discussion (void)unused_var; is in LLVM style guide, when we have c++ 17 we can use [[maybe_unused]] attribute. |
not really used in this revision?