✨ Add the quantum-ipo pipeline scheduling the interprocedural passes - #2201
Open
DRovara wants to merge 1 commit into
Open
✨ Add the quantum-ipo pipeline scheduling the interprocedural passes#2201DRovara wants to merge 1 commit into
quantum-ipo pipeline scheduling the interprocedural passes#2201DRovara wants to merge 1 commit into
Conversation
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 20, 2026 18:33
50c0eb6 to
714bb80
Compare
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 24, 2026 09:33
714bb80 to
0078ba5
Compare
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 24, 2026 09:52
0078ba5 to
816ffaf
Compare
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 25, 2026 07:50
816ffaf to
561dfe2
Compare
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 25, 2026 08:02
561dfe2 to
6d97f70
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 25, 2026 10:48
6d97f70 to
c60282d
Compare
burgholzer
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 25, 2026 21:44
c60282d to
161f694
Compare
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 26, 2026 14:08
161f694 to
8a9261f
Compare
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
2 times, most recently
from
August 26, 2026 14:34
d4cc42a to
e919f21
Compare
DRovara
marked this pull request as ready for review
August 26, 2026 14:37
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 27, 2026 11:40
e919f21 to
7099447
Compare
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 27, 2026 13:16
37144c5 to
3d83792
Compare
DRovara
force-pushed
the
mlir/quantum-ipo-pipeline
branch
2 times, most recently
from
August 28, 2026 08:11
1c8c185 to
58e8572
Compare
burgholzer
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 28, 2026 12:30
58e8572 to
f4edd2d
Compare
Register the interprocedural optimization sequence and cover direct and named pipeline execution. Assisted-by: Claude Opus 5 <noreply@anthropic.com> Assisted-by: Codex
burgholzer
force-pushed
the
mlir/quantum-ipo-pipeline
branch
from
August 30, 2026 14:21
f4edd2d to
16f4abb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 AI text below 🤖
Description
Last of the stack replacing #1970. Builds on #2200. Once this lands, #1970 can be closed as superseded.
populateQuantumIPOPipelineruns the four passes in the order they compose, registered as thequantum-ipopipeline. Commutation runs twice because it can expose further cancellations. The passes stay individually registered, so a caller assembling its own pipeline can pick only the ones it wants.test_qco_quantum_ipo.cppnow holds only the scenarios that need more than one pass; everything about a single pass lives in that pass's own suite. This is the review comment on the original PR actioned across the whole series — previously most per-pass cases ran through the full pipeline, which made it hard to tell which stage established a result and let one stage mask a regression in another.Splitting them found a real instance of exactly that: a promotion case in #2198 was passing only because the preceding pass's greedy pattern driver incidentally folded the IR first.
The changelog entry for the whole series now lives in the infrastructure PR #2194.
Testing
Three cross-stage cases live here; the complete optimization suite passes all 246 tests.
AI assistance
Code and this description were produced with Claude Code (Opus 5) and Codex, acting on my instructions and within the scope I authorized.
Checklist
If PR contains AI-assisted content:
🤖 *AI text below* 🤖(titles are exempt).