[Memory-layout infra] Create common permute fusing passes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
Create a set of well designed general passes for permute fusing. These can be based on existing passes.
- Passes should do one easily understandable thing. You want to be able to predict the output from the pass.
- Prefer one single general solution over many edge-cases where possible.
- Passes should be easily read and well documented.
- Passes may not depend on any backend-specific assumptions
The goal for this task is to reach a net count of 0 or less for the number of permutes before/ after running the convertion to exir_ops.edge.channels_last dialect over the full permute count test-suite created in #20097.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the full permute count test suite created in #20097 and compare counts before and after conversion to the exir_ops.edge.channels_last dialect. Review existing permute-fusing passes as possible foundations, keeping the desired behavior backend-independent and each pass easy to predict. Done means the suite reaches a net permute count of zero or less and the passes are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100