numba-enzyme-cuda 0.2.0__tar.gz

numba_enzyme_cuda-0.2.0/.github/workflows/detect-changes.yml

@@ -0,0 +1,31 @@
+name: Detect changes
+# Reusable workflow: computes whether files relevant to the test suite
+# changed in this pull request.
+
+on:
+  workflow_call:
+    outputs:
+      tests-relevant:
+        description: Whether files relevant to the test suite changed.
+        value: ${{ jobs.detect.outputs.tests-relevant }}
+
+jobs:
+  detect:
+    runs-on: ubuntu-latest
+    outputs:
+      tests-relevant: ${{ steps.filter.outputs.tests-relevant }}
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: dorny/paths-filter@v4
+        id: filter
+        with:
+          filters: |
+            tests-relevant:
+              - 'src/**'
+              - 'tests/**'
+              - 'pyproject.toml'
+              - 'uv.lock'
+              - 'packaging/build_enzyme_plugin.sh'
+              - '.github/workflows/tests.yml'
+              - '.github/workflows/detect-changes.yml'

numba_enzyme_cuda-0.2.0/.github/workflows/release.yml

@@ -0,0 +1,63 @@
+name: Release to PyPI
+
+# Tags own the release. `wheels.yml` builds the toolchain from source in the
+# manylinux image and is kept for verifying that path and for TestPyPI, but it
+# no longer publishes on a tag: two workflows uploading the same version would
+# race, and the second would fail on a file PyPI already has.
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+
+      # No cibuildwheel and no Docker: hatch_build.py stages the LLVM 15 +
+      # Enzyme binaries out of upstream's released manylinux wheel, which is
+      # where they come from either way, and the result is the same
+      # self-contained ~71 MB wheel -- under PyPI's 100 MB per-file limit.
+      - name: Build the sdist and wheel
+        run: uv build
+
+      - name: Check the metadata PyPI will read
+        run: uvx twine check --strict dist/*
+
+      # The wheel is only worth anything if the toolchain inside it survived
+      # the build with its permissions intact, and nothing else here would
+      # notice if it had not.
+      - name: Check the vendored toolchain runs
+        run: |
+          python -m zipfile -e dist/*.whl unpacked/
+          chmod +x unpacked/numba_enzyme/_vendor/bin/*
+          unpacked/numba_enzyme/_vendor/bin/clang --version
+          unpacked/numba_enzyme/_vendor/bin/opt --version
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    # Trusted publishing: PyPI mints a short-lived token from this workflow's
+    # OIDC identity, so no API token lives in the repository. A publisher for
+    # numba-enzyme-cuda naming this workflow file and environment has to exist
+    # on the PyPI side first.
+    environment:
+      name: pypi
+      url: https://pypi.org/p/numba-enzyme-cuda
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

numba_enzyme_cuda-0.2.0/.github/workflows/tests.yml

@@ -0,0 +1,68 @@
+name: Tests
+# Runs the actual `numba_enzyme` test suite on every pull request.
+#
+# LLVM 15 is no longer served by apt.llvm.org for any *current*
+# Ubuntu/Debian codename (its supported window has moved on) --
+# so this job runs inside a plain debian:trixie container and reuses
+# the exact same pinned apt.llvm.org bookworm-15 channel that
+# packaging/Dockerfile.manylinux already uses successfully. The
+# Enzyme plugin itself is built at enzyme-build/ via
+# packaging/build_enzyme_plugin.sh, which is exactly where toolchain.py's
+# default resolution already looks -- matching how every dev box
+# is already set up, so no NUMBA_ENZYME_PLUGIN_PATH override is
+# needed here either.
+
+on:
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  detect-changes:
+    uses: ./.github/workflows/detect-changes.yml
+
+  test:
+    name: Test
+    needs: detect-changes
+    if: needs.detect-changes.outputs.tests-relevant == 'true' || github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    container: debian:trixie
+    steps:
+      - name: Install git
+        run: apt-get update && apt-get install -y --no-install-recommends git ca-certificates
+
+      - uses: actions/checkout@v4
+
+      - name: Mark workspace as a safe git directory
+        run: git config --global --add safe.directory "$GITHUB_WORKSPACE"
+
+      - name: Install LLVM 15 + build tools
+        run: |
+          apt-get update && apt-get install -y --no-install-recommends \
+              curl gnupg ca-certificates cmake build-essential
+          curl -fsSL https://apt.llvm.org/llvm-snapshot.gpg.key \
+              | gpg --dearmor -o /usr/share/keyrings/llvm-archive-keyring.gpg
+          echo "deb [signed-by=/usr/share/keyrings/llvm-archive-keyring.gpg] http://apt.llvm.org/bookworm/ llvm-toolchain-bookworm-15 main" \
+              > /etc/apt/sources.list.d/llvm-15.list
+          apt-get update && apt-get install -y --no-install-recommends \
+              llvm-15-dev clang-15 lld-15
+          rm -rf /var/lib/apt/lists/*
+
+      - name: Cache Enzyme plugin build
+        uses: actions/cache@v4
+        id: enzyme-cache
+        with:
+          path: enzyme-build
+          key: enzyme-v0.0.289-llvm15-${{ runner.os }}
+
+      - name: Build standalone Enzyme plugin
+        if: steps.enzyme-cache.outputs.cache-hit != 'true'
+        run: bash packaging/build_enzyme_plugin.sh enzyme-build
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v9.0.0
+
+      - name: Run tests
+        run: uv run pytest -v
+
+      - name: Run pre-commit
+        run: uv run pre-commit run --all-files

numba_enzyme_cuda-0.2.0/.github/workflows/wheels.yml

@@ -0,0 +1,110 @@
+name: Build and publish wheels
+
+# Not on tags: release.yml owns those, and two workflows uploading one version
+# would race. This one stays for building the toolchain from source in the
+# manylinux image, and for TestPyPI.
+on:
+  workflow_dispatch:
+
+jobs:
+  build-image:
+    name: Build manylinux container image
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: docker/setup-buildx-action@v3
+
+      # Cached via GHA's own cache backend -- the image build compiles
+      # three CPython versions from source, expensive enough to be
+      # worth caching aggressively between runs.
+      - uses: docker/build-push-action@v6
+        with:
+          context: .
+          file: packaging/Dockerfile.manylinux
+          tags: numba-enzyme-manylinux:latest
+          push: false
+          load: true
+          cache-from: type=gha
+          cache-to: type=gha,mode=max
+
+      - name: Save image for later jobs
+        run: docker save numba-enzyme-manylinux:latest -o /tmp/numba-enzyme-manylinux.tar
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: manylinux-image
+          path: /tmp/numba-enzyme-manylinux.tar
+          retention-days: 1
+
+  build-wheels:
+    name: Build wheels
+    needs: build-image
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/download-artifact@v4
+        with:
+          name: manylinux-image
+          path: /tmp
+
+      - name: Load manylinux image
+        run: docker load -i /tmp/numba-enzyme-manylinux.tar
+
+      # Pinned to the exact version (4.1.1) for cp39-cp39
+      # compatibility.
+      - name: Build wheels
+        uses: pypa/cibuildwheel@v4.1.1
+        env:
+          CIBW_MANYLINUX_X86_64_IMAGE: numba-enzyme-manylinux:latest
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: wheels
+          path: wheelhouse/*.whl
+
+      - name: Report wheel sizes
+        run: ls -lh wheelhouse/*.whl
+
+  publish-testpypi:
+    name: Publish to TestPyPI
+    needs: build-wheels
+    if: github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    environment:
+      name: testpypi
+      url: https://test.pypi.org/p/numba-enzyme-cuda
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: wheels
+          path: wheelhouse
+
+      - uses: pypa/gh-action-pypi-publish@v1.14.2
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          packages-dir: wheelhouse
+
+  # Kept for a from-source release done by hand; the tag path is release.yml.
+  publish-pypi:
+    name: Publish to PyPI
+    needs: build-wheels
+    if: false
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/numba-enzyme-cuda
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: wheels
+          path: wheelhouse
+
+      - uses: pypa/gh-action-pypi-publish@v1.14.2
+        with:
+          packages-dir: wheelhouse

numba_enzyme_cuda-0.2.0/.gitignore

@@ -0,0 +1,22 @@
+.venv/
+.dev-toolchain/
+__pycache__/
+*.pyc
+enzyme-src/
+enzyme-build/
+*.so
+*.ll
+.pytest_cache/
+.ruff_cache/
+bk/
+
+# _vendor/ is the LLVM 15 + Enzyme toolchain, 237 MB staged at wheel-build
+# time and never committed. It used to be un-ignored, so that the blanket
+# `*.so` above could not make an sdist-based frontend silently ship a wheel
+# with no Enzyme plugin. hatch_build.py closed that hole from the other end:
+# it force-includes every _vendor/ file, which bypasses VCS ignore rules
+# entirely, and restages the toolchain from the released PyPI wheel whenever
+# the directory is missing -- so a wheel built from an sdist that excludes
+# _vendor/ still comes out complete. Ignoring it keeps `git status` readable
+# and the 237 MB un-committable.
+src/numba_enzyme/_vendor/

numba_enzyme_cuda-0.2.0/.pre-commit-config.yaml

@@ -0,0 +1,26 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.16.0
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+
+  - repo: https://github.com/numpy/numpydoc
+    rev: v1.10.0
+    hooks:
+      - id: numpydoc-validation
+        files: ^src/
+
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: check-yaml
+      - id: check-ast
+      - id: check-json
+      - id: check-merge-conflict
+      - id: debug-statements
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+      - id: check-added-large-files
+        args: ['--maxkb=3072']

numba_enzyme_cuda-0.2.0/LICENSE

@@ -0,0 +1,233 @@
+==============================================================================
+The LLVM Project is under the Apache License v2.0 with LLVM Exceptions:
+As a project hoping to become part of LLVM, Enzyme is under the same license.
+==============================================================================
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+---- LLVM Exceptions to the Apache 2.0 License ----
+
+As an exception, if, as a result of your compiling your source code, portions
+of this Software are embedded into an Object form of such source code, you
+may redistribute such embedded portions in such Object form without complying
+with the conditions of Sections 4(a), 4(b) and 4(d) of the License.
+
+In addition, if you combine or link compiled forms of this Software with
+software that is licensed under the GPLv2 ("Combined Software") and if a
+court of competent jurisdiction determines that the patent provision (Section
+3), the indemnity provision (Section 9) or other Section of the License
+conflicts with the conditions of the GPLv2, you may retroactively and
+prospectively choose to deem waived or otherwise exclude such Section(s) of
+the License, but only in their entirety and only with respect to the Combined
+Software.
+
+==============================================================================
+Software from third parties included in the LLVM Project:
+==============================================================================
+The LLVM Project contains third party software which is under different license
+terms. All such code will be identified clearly using at least one of two
+mechanisms:
+1) It will be in a separate directory tree with its own `LICENSE.txt` or
+   `LICENSE` file at the top containing the specific license and restrictions
+   which apply to that software, or
+2) It will contain specific license and restriction terms at the top of every
+   file.

numba_enzyme_cuda-0.2.0/NOTICE

@@ -0,0 +1,3 @@
+numba-enzyme
+
+Originally developed by Qruise GmbH (https://qruise.com).