The reifyReturnTypeShapesPerResultDim method supports shape
inference for rsults that are ranked types. These are used lower in
the codegeneration stack than its counter part reifyReturnTypeShapes
which also supports unranked types, and is more suited for use higher
up the compilation stack. To have separation of concerns, this method
is split into its own interface.
See discussion : https://llvm.discourse.group/t/better-layering-for-infershapedtypeopinterface/3823
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Looks like good cleanup thanks. I just focused interface side as I don't know the rest as well.
mlir/include/mlir/Interfaces/InferTypeOpInterface.td | ||
---|---|---|
150 | Not to bike shed, but is the additonal shape needed? ShapedType is the c++ class, and just ReifyRankedShapedTypeOpInterface seems descriptive and unambiguous | |
155 | Vector too correct? | |
165 | Indent more to avoid the document generator adding weird spaces :) | |
170 | The last sentence is probably not needed given interface name. | |
177 | OOC Should we perhaps add a typedef for this? |
Not to bike shed, but is the additonal shape needed?
ShapedType is the c++ class, and just ReifyRankedShapedTypeOpInterface seems descriptive and unambiguous