munich-quantum-toolkit / munich-quantum-toolkit/core-plugins-catalyst
⚗️ MLIR - Investigate loosening exact LLVM version pin for external plugins
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8
- Forks
- 2
- Avg merge
- 5h 27m
- Merged PRs (30d)
- 34
Description
Currently, the Catalyst Plugin CI requires installing LLVM from source (either through Catalyst from source or directly LLVM from source). This is not ideal as it takes forever. We should investigate at some point whether there is anything we can do to make this work with pre-compiled LLVM versions.
I'd still like to investigate at some point whether there is anything we can do to make this work with pre-compiled LLVM versions. But this will have to wait for a future PR. It would be great to create a tracking issue for this though.
Originally posted by @burgholzer in https://github.com/munich-quantum-toolkit/core/pull/881#discussion_r2244095704
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 Catalyst Plugin CI and its current LLVM-from-source installation path. Investigate whether external plugins can use pre-compiled LLVM versions without the exact version pin. Done means establishing the supported compatibility constraints and recording whether the CI setup can be changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, ci-cd, compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100