✨ Map QCO programs to compiler targets - #1997
Merged
Merged
Conversation
Assisted-by: GPT-5.6 via Codex
Assisted-by: GPT-5.6 via Codex
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
Assisted-by: GPT-5.6 via Codex
12 tasks
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
Replace the mapping pass’s duplicated topology wrapper with the immutable
mlir::CompilerTargetintroduced in #1993.The mapper consumes topology only. It keeps dense internal vertices for placement, A* routing, voting, and restoration; translates to provider-defined site IDs only when emitting
qco.static; and inserts ordinary symmetricqco.swapoperations without inspecting native capabilities, calibration, fidelities, durations, or gate direction.The refactor preserves the current #1951 vote-and-restore mapper while adding scalar, tensor, mixed, and qubit-reuse allocation support, noncontiguous hardware IDs, diagnostics for nested allocations and residual higher-arity operations, and sparse vacant workspace without materializing an entire large target in IR.
This is MAP-01 in the compact QDMI–Compiler integration series. Mapping now exposes only its target-taking factory. The current high-level
QCOProgram::placeAndRouteconstructs aCompilerTargetat its existing coupling-input boundary; PIPE-01 can remove that remaining high-level coupling API without touching Mapping again.The existing mapping changelog entry is extended; no upgrade note is needed for the unreleased compiler collection.
Validation
Checklist
If PR contains AI-assisted content:
🤖 *AI text below* 🤖(titles are exempt).