MLIR
The MLIR frontend contains a translation of core MLIR dialects to SDFGs. It also contains a custom linalg dialect extension to represent operations that are missing in the core linalg dialect of MLIR.
Build from Sources
To build the MLIR component from source install LLVM/MLIR dependencies first:
sudo apt-get install -y libmlir-21 libmlir-21-dev mlir-21-tools
Second, build from the root of the repository using cmake:
mkdir build && cd build
cmake -G Ninja \
-DCMAKE_C_COMPILER=clang-21 \
-DCMAKE_CXX_COMPILER=clang++-21 \
-DCMAKE_BUILD_TYPE=Debug \
-DMLIR_BUILD_FRONTEND=ON \
-DMLIR_BUILD_TESTS=ON \
-DMLIR_DIR=/usr/lib/llvm-21/lib/cmake/mlir \
-DLLVM_EXTERNAL_LIT=/usr/lib/llvm-21/build/utils/lit/lit.py \
-DWITH_SYMENGINE_THREAD_SAFE=ON \
-DWITH_SYMENGINE_RCP=ON \
-DINSTALL_GTEST=OFF \
-DBUILD_TESTS:BOOL=OFF \
-DBUILD_BENCHMARKS:BOOL=OFF \
-DBUILD_BENCHMARKS_GOOGLE:BOOL=OFF \
..
ninja -j$(nproc)
To verify, the basic dialects and translation work, run the tests:
ninja check-docc-mlir
License
This component is part of docc and is published under the BSD-3-Clause license. See LICENSE for details.
Metadata
Release files for docc-ai 0.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 151.7 MB
Release files / docc_ai-0.9.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | docc_ai-0.9.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 17.9 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
da008b0de7d6f2a8f8bf96d2968d7e39a530f145cf67af01a8be8bffea561bbb
|
|
BLAKE2b-256 checksum How to use checksums |
2d59a2b8d0bf71a717ebcfaa9238d832832fa3a8806c3216fcab81b9f2ce474e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 13, 2026.
Transparency logRelease files / docc_ai-0.9.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | docc_ai-0.9.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 17.1 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
5c955f63d2d232b2061e3a82a36a2b59bc2789b6e47790ff0ae8339e81c232cb
|
|
BLAKE2b-256 checksum How to use checksums |
936e1d88be082ee8204c33991cf46b0226f175e0f3333c14dfda9a99aa5f5715
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 13, 2026.
Transparency logRelease files / docc_ai-0.9.0-cp312-cp312-macosx_15_0_arm64.whl
| Download URL | docc_ai-0.9.0-cp312-cp312-macosx_15_0_arm64.whl |
|---|---|
| Size | 40.8 MB |
| Tags | CPython 3.12 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
60102024b2ee3802e21e3a5454b3e15ae0cfdc541b1dade0a41f7e621d4ff28f
|
|
BLAKE2b-256 checksum How to use checksums |
ea2dd67722411d839703a611616b1d27f4f55002eadd93542d4d71ef782b3d9d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 13, 2026.
Transparency logRelease files / docc_ai-0.9.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | docc_ai-0.9.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 17.9 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
dc1fa4d3a8b6fe879a0281eaf2f66e99fb0a927ecaf7b9ea666c0ea353709ef2
|
|
BLAKE2b-256 checksum How to use checksums |
8ffb585be2956fba50ed3f755847b79824e32eb6eb60de0578c063992250233c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 13, 2026.
Transparency logRelease files / docc_ai-0.9.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | docc_ai-0.9.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 17.1 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
020a06d0c693386f4a9cab5eda6053687135837839f7a06cf235df30f6088804
|
|
BLAKE2b-256 checksum How to use checksums |
7d291072d06cad4af82f4149edcfa657ea2525d65f691cf23e30631454b6c697
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 13, 2026.
Transparency logRelease files / docc_ai-0.9.0-cp311-cp311-macosx_15_0_arm64.whl
| Download URL | docc_ai-0.9.0-cp311-cp311-macosx_15_0_arm64.whl |
|---|---|
| Size | 40.8 MB |
| Tags | CPython 3.11 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
e4fffe344fcf5dffc2f8841dcf9073bf4e58174d28b5be11ae0c95e9c10b372e
|
|
BLAKE2b-256 checksum How to use checksums |
67d18f85bfd811270150035d35992fab4a8fdfa0621e8cbad72aef036c9a5e29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 13, 2026.
Transparency logSecurity for docc-ai 0.9.0
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.
Full provenance
All 6 files in this release have been uploaded with provenance metadata.
Attestation for docc_ai-0.9.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
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 Nov 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
