See this documentation from taco:
http://tensor-compiler.org/docs/data_analytics/index.html
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/test/Integration/Dialect/SparseTensor/CPU/sparse_mttkrp.mlir | ||
---|---|---|
45 | even though "mlir" code does not has a style guideline, try to avoid 80 col overwrap (here and below). Not a hard rule, just easier to read in browsers. | |
71 | Here and below, period at end of comment | |
mlir/test/Integration/data/mttkrp_b.tns | ||
18 | The double ## makes sense since we have a comment inside a comment, but is there a better way to make this jump out a bit more? Also, we have the style guideline to end each comment with a period (full sentence). |
Address Aart's comments: line length, add periods, make code comment stand out
mlir/test/Integration/data/mttkrp_b.tns | ||
---|---|---|
18 | I tried adding >s. Let me know if that makes it any more clear, otherwise I'll try something else! |
mlir/test/Integration/data/mttkrp_b.tns | ||
---|---|---|
18 | yeah. looks good. thanks! |
Oh, in this and the previous commit, I forgot to say that we usually add tags to the title of a revision (typically [mlir] followed by a sub-component).
I usually add [mlir][sparse] for anything related to sparse tensor compilation. I have added this to the title for this revision.
even though "mlir" code does not has a style guideline, try to avoid 80 col overwrap (here and below). Not a hard rule, just easier to read in browsers.