⬆️🩹 Update munich-quantum-toolkit/workflows action to v1.17.15#1549
⬆️🩹 Update munich-quantum-toolkit/workflows action to v1.17.15#1549denialhaag merged 22 commits intomainfrom
Conversation
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
|
Okay, this seems to be mostly working so far 🎉 |
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
Signed-off-by: burgholzer <burgholzer@me.com>
0cdf66d to
ce202fc
Compare
|
Okay, turns out the changes from ea0d2a2 are not backwards compatible as there have been breaking changes in the underlying interfaces. |
Signed-off-by: burgholzer <burgholzer@me.com>
…ptions target Signed-off-by: burgholzer <burgholzer@me.com>
|
Apart from some flukes on macOS x GCC, all tests are passing. I'm removing the extensive label again. |
📝 WalkthroughWalkthroughUpdated CI reusable workflows to v1.17.15, bumped LLVM/MLIR requirement to 22.1, replaced builder.create usages with static Op::create(...) across MLIR code, tightened several CMake link visibilities to PRIVATE, and added a runStage wrapper in the compiler pipeline. Changes
Sequence Diagram(s)sequenceDiagram
participant Caller as CompilerPipeline
participant Wrapper as runStage
participant PM as PassManager
participant Module as MLIR Module
Caller->>Wrapper: runStage(stageName, populateFn)
Wrapper->>PM: create local PassManager
Wrapper->>PM: apply diagnostics/config
Wrapper->>PM: call populateFn(PM)
PM->>Module: run passes on Module
PM-->>Wrapper: return success/failure
Wrapper-->>Caller: return stage result
Estimated code review effort🎯 4 (Complex) | ⏱️ ~50 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.readthedocs.yaml:
- Line 35: Replace the mutable branch ref in the curl command that fetches
setup-mlir.sh with a specific release tag; locate the line that calls "curl
-LsSf
https://raw.githubusercontent.com/munich-quantum-software/setup-mlir/refs/heads/bump-package-version/installation/setup-mlir.sh
| bash -s -- -v 22.1.0 -p $HOME/mlir" and change the path segment
"refs/heads/bump-package-version" to a stable tag (for example
"refs/tags/v1.3.0" or the tag that matches MLIR 22.1.0) so the installer URL
points to an immutable release.
In `@cmake/SetupMLIR.cmake`:
- Around line 12-14: Add an UPGRADING.md entry that explains the new MLIR/LLVM
minimum version set by MQT_MLIR_MIN_VERSION ("22.1"), describes the user impact
(source builds that used older MLIR/LLVM may break), and points users to the
project's supported prebuilt LLVM/MLIR distributions and migration steps
(installing the prebuilt, updating LLVM/MLIR paths, or rebuilding with the newer
toolchain); reference the CHANGELOG.md entry and include precise instructions
for where to change build variables or environment variables so downstream
builders can migrate smoothly.
In `@mlir/unittests/programs/CMakeLists.txt`:
- Around line 24-25: The target MLIRQuantumComputationPrograms currently exports
MQT::ProjectOptions as a PUBLIC dependency; change the linkage so MQT::CoreIR
remains PUBLIC (API dependency) but MQT::ProjectOptions is linked PRIVATE to
avoid propagating compiler/linker flags. Update the target_link_libraries call
for MLIRQuantumComputationPrograms to reference MQT::CoreIR as PUBLIC and
MQT::ProjectOptions as PRIVATE.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: d38715bd-2593-4b5e-b806-b9b72d363a64
📒 Files selected for processing (19)
.github/workflows/cd.yml.github/workflows/ci.yml.github/workflows/upstream.yml.pre-commit-config.yaml.readthedocs.yamlAGENTS.mdCHANGELOG.mdcmake/ExternalDependencies.cmakecmake/SetupMLIR.cmakemlir/lib/Compiler/CompilerPipeline.cppmlir/lib/Conversion/QCToQIR/QCToQIR.cppmlir/lib/Dialect/QC/IR/CMakeLists.txtmlir/lib/Dialect/QC/IR/Modifiers/CtrlOp.cppmlir/lib/Dialect/QCO/IR/CMakeLists.txtmlir/lib/Dialect/QCO/IR/SCF/IfOp.cppmlir/lib/Dialect/QCO/Transforms/CMakeLists.txtmlir/lib/Dialect/QIR/Utils/QIRUtils.cppmlir/unittests/programs/CMakeLists.txtpyproject.toml
|
@burgholzer, given that CodeRabbit and CI are happy, I'd say we can merge this now. 🤔 |
Yeah. Just had a final look and this should be good to go! 🚀 |
Description
This PR updates the MQT Workflows to their latest version, which contains fixes for the
setup-mliraction that should unblock the CI here.This PR furthermore updates the LLVM version to 22.1.0 and aims to fix all issues popping up based on that.
Checklist:
I have added appropriate tests that cover the new/changed functionality.I have updated the documentation to reflect these changes.