Support injecting MLIR passes in JIT compilation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
Required prerequisites
- Search the issue tracker to check if your feature has already been mentioned or rejected in other issues.
Describe the feature
Injecting a custom MLIR pass into cudaq-opt is possible, as described here. It would also be useful to inject custom passes into the JIT compiler, for compilation of runtime kernels and for Python support.
In addition, it would be useful to support defining the pass order to be run by the JIT compiler. In particular, requiring that some passes are run before the custom pass.
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 MLIR pass injection documentation for cudaq-opt linked in the issue, then trace how the JIT compiler handles runtime kernels and Python support. Determine the entry points for registering custom passes and defining their order, including required passes that must run first. Done means custom passes can be injected into both stated JIT paths with controllable ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100