Google GitGoogle Git
Sign in
apache/tvm-ffi/3d33014ba11fb5556fcd10a9cc11a540dd799443
commit
3d33014ba11fb5556fcd10a9cc11a540dd799443
[log]
author
Junru Shao <junrushao@apache.org>
Wed Apr 08 00:23:40 2026 -0700
committer
GitHub <noreply@github.com>
Wed Apr 08 15:23:40 2026 +0800
tree
479b709360280b0af37b67a1d93043c0b6239dbc
parent
1a305b63b17f41695c97d379dff96c6169cdb209 [diff]
build(deps): replace cmake version exclusion with uv exclude-newer (#526)

Remove the `cmake\!=4.3.1` version pin from dev dependencies and instead
add a `[tool.uv] exclude-newer = "14 days"` setting. This prevents
installing any package released within the last 14 days, which is a more
general and maintainable approach to avoiding freshly-released broken
packages across the entire dependency tree.

- Architecture: No changes.
- Public Interfaces: No changes.
- UI/UX: No changes.
- Behavioral Changes: `uv` will now exclude packages newer than 14 days
for all resolution, not just cmake. The cmake-specific version exclusion
is removed.
- Docs: No changes needed (build config only).
- Tests: No changes needed (config-only change).
- Untested Edge Cases: The `exclude-newer` directive is relative ("14
days"), so resolution results will vary by the date `uv` is invoked. CI
reproducibility depends on lockfile presence.
1 file changed
tree: 479b709360280b0af37b67a1d93043c0b6239dbc
  1. .claude/
  2. .github/
  3. 3rdparty/
  4. addons/
  5. cmake/
  6. docs/
  7. examples/
  8. include/
  9. licenses/
  10. python/
  11. rust/
  12. src/
  13. tests/
  14. .asf.yaml
  15. .clang-format
  16. .clang-tidy
  17. .cmake-format.json
  18. .gitignore
  19. .gitmodules
  20. .markdownlint-cli2.yaml
  21. .pre-commit-config.yaml
  22. .yamllint.yaml
  23. CLAUDE.md
  24. CMakeLists.txt
  25. CONTRIBUTING.md
  26. KEYS
  27. LICENSE
  28. NOTICE
  29. pyproject.toml
  30. README.md
README.md

TVM FFI: Open ABI and FFI for Machine Learning Systems

📚 Documentation | 🚀 Quickstart

Apache TVM FFI is an open ABI and FFI for machine learning systems. It is a minimal, framework-agnostic, yet flexible open convention with the following systems in mind:

  • Kernel libraries - ship one wheel to support multiple frameworks, Python versions, and different languages. [FlashInfer]
  • Kernel DSLs - reusable open ABI for JIT and AOT kernel exposure frameworks and runtimes. [TileLang][cuteDSL]
  • Frameworks and runtimes - a uniform extension point for ABI-compliant libraries and DSLs. [PyTorch][JAX][PaddlePaddle][NumPy/CuPy]
  • ML infrastructure - out-of-box bindings and interop across languages. [Python][C++][Rust]
  • Coding agents - a unified mechanism for shipping generated code in production.

Features

  • Stable, minimal C ABI designed for kernels, DSLs, and runtime extensibility.
  • Zero-copy interop across PyTorch, JAX, and CuPy using DLPack protocol.
  • Compact value and call convention covering common data types for ultra low-overhead ML applications.
  • Multi-language support out of the box: Python, C++, and Rust (with a path towards more languages).

These enable broad interoperability across frameworks, libraries, DSLs, and agents; the ability to ship one wheel for multiple frameworks and Python versions (including free-threaded Python); and consistent infrastructure across environments.

Getting Started

Install TVM-FFI with pip, uv or from source:

pip install apache-tvm-ffi
pip install torch-c-dlpack-ext  # compatibility package for torch <= 2.9

Status and Release Versioning

C ABI stability is our top priority.

Status: RFC Main features are complete and ABI stable. We recognize potential needs for evolution to ensure it works best for the machine learning systems community, and would like to work together with the community for such evolution. We plan to stay in the RFC stage for three months from the v0.1.0 release.

Releases during the RFC stage will be 0.X.Y, where bumps in X indicate C ABI-breaking changes and Y indicates other changes. We anticipate the RFC stage will last for three months, then we will start following Semantic Versioning (major.minor.patch) going forward.

Documentation

Our documentation site includes:

Get Started

Guides

Concepts

Packaging

Developer Manual