munich-quantum-toolkit / munich-quantum-toolkit/core-plugins-catalyst
✨ MLIR - Decouple Pass and Dialect Plugin
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8
- Forks
- 2
- Avg merge
- 5h 27m
- Merged PRs (30d)
- 34
Description
Problem Statement
When loading a MLIR plugin, the optimization tool must be provided with two options --load-pass-plugin and --load-dialect-plugin. As of now, we pass the same .dylib to both options.
Proposed Solution
I am not certain whether this gives any advantage but it might be worth it to try out to decouple the pass and dialect plugin into two separate dynamic libraries.
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 by reviewing how the optimization tool currently receives --load-pass-plugin and --load-dialect-plugin, including where the same .dylib is supplied to both. Determine whether separating the pass and dialect plugins provides a benefit and identify the project entry points involved. Done means the desired separation and its acceptance criteria are agreed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100