Skip to content

🚧 Specify QPU Architecture via arch option#1687

Draft
MatthiasReumann wants to merge 2 commits into
mainfrom
feat/arch-option-and-qdmi
Draft

🚧 Specify QPU Architecture via arch option#1687
MatthiasReumann wants to merge 2 commits into
mainfrom
feat/arch-option-and-qdmi

Conversation

@MatthiasReumann
Copy link
Copy Markdown
Collaborator

@MatthiasReumann MatthiasReumann commented May 6, 2026

Description

This is a work-in-progress pull request adding an arch option to the mqt-cc tool that specifies the target QPU architecture / device. Eventually, the provided name should be used to load a dynamic device library and setup the QDMI device accordingly.

If the architecture option is provided, the mqt-cc tool should perform transpilation. That is native gate-set decomposition, and if the architecture has a coupling map, the superconducting mapping pass1. Otherwise, these steps are skipped and the compilation is thus hardware-agnostic.

My hope is that by doing / discussing this now, we can immediately test and benchmark multiple architectures more easily.

Resolves #1082.

Checklist

  • The pull request only contains commits that are focused and relevant to this change.
  • I have added appropriate tests that cover the new/changed functionality.
  • I have updated the documentation to reflect these changes.
  • I have added entries to the changelog for any noteworthy additions, changes, fixes, or removals.
  • I have added migration instructions to the upgrade guide (if needed).
  • The changes follow the project's style guidelines and introduce no new warnings.
  • The changes are fully tested and pass the CI checks.
  • I have reviewed my own code changes.

If PR contains AI-assisted content:

  • I have disclosed the use of AI tools in the PR description as per our AI Usage Guidelines.
  • AI-assisted commits include an Assisted-by: [Model Name] via [Tool Name] footer.
  • I confirm that I have personally reviewed and understood all AI-generated content, and accept full responsibility for it.

Footnotes

  1. --fit-topology (or --fit-coupling-map) could potentially be a more suitable name instead of the generic --place-and-route.

@MatthiasReumann MatthiasReumann self-assigned this May 6, 2026
@MatthiasReumann MatthiasReumann added c++ Anything related to C++ code MLIR Anything related to MLIR labels May 6, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented May 6, 2026

Codecov Report

❌ Patch coverage is 17.64706% with 14 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
mlir/lib/Compiler/CompilerPipeline.cpp 17.6% 14 Missing ⚠️

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c++ Anything related to C++ code MLIR Anything related to MLIR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

✨ MLIR - Feeding Architecture Information into MLIR Mapping Conversion

1 participant