KIRIN
Kernel Intermediate Representation INfrastructure
[!IMPORTANT]
This project is in the early stage of development. API and features are subject to change. If you are concerned about the stability of the APIs, consider pinning the version of Kirin in your project.
Installation
Install via uv (Recommended)
uv add kirin-toolchain
Install via pip
pip install kirin-toolchain
Documentation
The documentation is available at https://queracomputing.github.io/kirin/latest/. We are at an early stage of completing the documentation with more details and examples, so comments and contributions are most welcome!
Community
- Slack: join our Slack.
- GitHub Discussions: discussion board for questions, feature requests, and more. GitHub Discussions.
Projects using Kirin
Quantum Computing
We are actively using Kirin at QuEra Computing. Here are some open-source eDSLs for quantum computing that we have developed using Kirin:
- bloqade.qasm2: This is an eDSL for quantum computing that uses Kirin to define an eDSL for the Quantum Assembly Language (QASM) 2.0. It demonstrates how to create multiple dialects using Kirin, run custom analysis and rewrites, and generate code from the dialects (back to QASM 2.0 in this case).
- bloqade.stim: This is an eDSL for quantum computing that uses Kirin to define an eDSL for the STIM language. It demonstrates how to create multiple dialects using Kirin, run custom analysis and rewrites, and generate code from the dialects (back to Stim in this case).
- bloqade.qBraid: This example demonstrates how to lower from an existing representation into the Kirin IR by using the visitor pattern.
Roadmap
We use github issues to track the roadmap. There are more feature requests and proposals in the issues. Here are some of the most wanted features we wish to implement before a beta release:
- Initial version of the IR
- Interpretation framework
- Basic analysis and transformations (e.g. constant folding, type inference, etc.)
- Documentation
- proper stack trace for errors (#13)
- text format (#199)
- Integration with LLVM (#294)
- Integration with MLIR (IRDL) (#293)
- IR serialization + deserialization (#291)
Proposal for the roadmap and feature requests are welcome!
License
Apache License 2.0 with LLVM Exceptions
1 maintainer
Metadata
1 maintainer
Release files for kirin-toolchain 0.22.16
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| kirin_toolchain-0.22.16.tar.gz | 1.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kirin_toolchain-0.22.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 MB
Release files / kirin_toolchain-0.22.16.tar.gz
| Download URL | kirin_toolchain-0.22.16.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2d308d0f7e229e508a227846db0659c14789057d519572941b7785bd9096eb6
|
|
BLAKE2b-256 checksum How to use checksums |
85dc825a8abad47abd3eb7268060fe90719c61ffdc4246920f2aa20c0b0c24d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency logRelease files / kirin_toolchain-0.22.16-py3-none-any.whl
| Download URL | kirin_toolchain-0.22.16-py3-none-any.whl |
|---|---|
| Size | 264.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
afcc09abaf8460858bcc2a42035919dd67ffe49fe242c560613de2a42e5969d9
|
|
BLAKE2b-256 checksum How to use checksums |
56f841e0ba5d16a35531d09f90315ac7aee9472adcc76c0ad03896693824772f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency log
