This is useful as it is sometimes better to try to canonicalize the transpose away after contract lowering rather than lowering it to a chain of scalar insert/extract.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
shouldn't we instead omit the transpose lowering pattern in places where don't want to apply it?
Comment Actions
Do you mean adding a if() addPattern<TransposeLowering> in or split the populateVectorContractLoweringPatterns? Splitting it would make sense, I just need to make sure every user gets updated.
Comment Actions
Changed it to a NFC change moving transpose lowering in a separate populate function.