The Torch-MLIR project aims to provide first class support from the PyTorch ecosystem to the MLIR ecosystem.
 
 
 
 
 
 
Go to file
Prathamesh Tagore 617c1c76ce
[torch.bind_symbolic_shape] Fix verifier for shapeSymbol detection (#3751)
The op can be valid with no attached shape symbols if they are not
required by the corresponding affine map. Fix the verifier to consider
number of arguments for both.
2024-10-02 05:55:54 -07:00
.github build: Update Roll PyTorch version (#3548) 2024-07-19 21:38:57 +05:30
build_tools [ci] enable fx_importer2stablehlo ci test (#3698) 2024-09-11 09:53:23 +08:00
docs Update instructions on creating a virtual env (#3724) 2024-10-01 19:12:11 +02:00
externals bump llvm/llvm-project@d418a03e01 (#3700) 2024-09-11 11:42:31 -04:00
include [Torch] support binary_cross_entropy_with_logits decomposition (#3741) 2024-09-29 17:41:20 +08:00
lib [torch.bind_symbolic_shape] Fix verifier for shapeSymbol detection (#3751) 2024-10-02 05:55:54 -07:00
projects [TOSA] Add legalization for aten.diagonal (#3740) 2024-09-30 08:24:31 -07:00
python Redefine TorchMLIRPythonModules to avoid building empty libraries. (#3711) 2024-09-13 10:41:34 -07:00
test [torch.bind_symbolic_shape] Fix verifier for shapeSymbol detection (#3751) 2024-10-02 05:55:54 -07:00
tools Link necessary op interface implementations (#3364) 2024-06-03 19:43:28 -05:00
utils/bazel [Bazel] Add BuiltinDialectTdFiles dep to MLIRTorchOpsIncGen (#3430) 2024-06-07 05:02:17 -07:00
.clang-format Add stub numpy dialect. 2020-04-26 17:20:58 -07:00
.git-blame-ignore-revs Add .git-blame-ignore-revs to allow ignoring sweeping formatting changes (#2823) 2024-01-29 10:29:51 -08:00
.gitignore [Pipeline] Use dedicated simplification pipeline for TorchDynamo frontend (#3376) 2024-05-22 05:23:18 -07:00
.gitmodules Revert accidental change to submodule origin. (#2477) 2023-09-20 14:05:52 +08:00
.pre-commit-config.yaml [NFC] Update black version (#3256) 2024-04-29 11:06:01 +08:00
.yamllint.yml Add `.yamllint` and disable some annoying recurring warnings on every pr (#3224) 2024-04-30 21:48:01 +00:00
CITATION.cff Add CITATION file (#2371) 2023-08-02 14:36:15 -07:00
CMakeLists.txt Redefine TorchMLIRPythonModules to avoid building empty libraries. (#3711) 2024-09-13 10:41:34 -07:00
LICENSE Dual license the torch-mlir project. 2021-10-01 10:46:08 -07:00
README.md Disable TORCH_MLIR_ENABLE_JIT_IR_IMPORTER and TORCH_MLIR_ENABLE_PYTORCH_EXTENSIONS by default (#3693) 2024-09-09 22:58:27 -07:00
build-requirements.txt [arm64] Fix release builds for ARM64 (#2157) 2023-05-24 13:52:13 -07:00
pyproject.toml Switch to pre-commit for lint checks. (#3200) 2024-04-27 13:29:51 -07:00
pytorch-hash.txt build: manually update PyTorch version (#3715) 2024-09-18 12:00:15 +05:30
pytorch-requirements.txt build: manually update PyTorch version (#3715) 2024-09-18 12:00:15 +05:30
requirements.txt python: separate build- and test-related pip dependencies (#1874) 2023-02-13 21:22:09 -06:00
setup.py Redefine TorchMLIRPythonModules to avoid building empty libraries. (#3711) 2024-09-13 10:41:34 -07:00
test-requirements.txt Bump Onnx Version to 1.16.1 (#3515) 2024-07-01 22:15:45 +05:30
torchvision-requirements.txt build: manually update PyTorch version (#3715) 2024-09-18 12:00:15 +05:30
whl-requirements.txt Add ARM64 release builds (#2159) 2023-05-25 20:39:19 -07:00

README.md

The Torch-MLIR Project

The Torch-MLIR project aims to provide first class compiler support from the PyTorch ecosystem to the MLIR ecosystem.

This project is participating in the LLVM Incubator process: as such, it is not part of any official LLVM release. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project is not yet endorsed as a component of LLVM.

PyTorch PyTorch is an open source machine learning framework that facilitates the seamless transition from research and prototyping to production-level deployment.

MLIR The MLIR project offers a novel approach for building extensible and reusable compiler architectures, which address the issue of software fragmentation, reduce the cost of developing domain-specific compilers, improve compilation for heterogeneous hardware, and promote compatibility between existing compilers.

Torch-MLIR Several vendors have adopted MLIR as the middle layer in their systems, enabling them to map frameworks such as PyTorch, JAX, and TensorFlow into MLIR and subsequently lower them to their target hardware. We have observed half a dozen custom lowerings from PyTorch to MLIR, making it easier for hardware vendors to focus on their unique value, rather than needing to implement yet another PyTorch frontend for MLIR. The ultimate aim is to be similar to the current hardware vendors adding LLVM target support, rather than each one implementing Clang or a C++ frontend.

pre-commit

All the roads from PyTorch to Torch MLIR Dialect

We have few paths to lower down to the Torch MLIR Dialect.

  • ONNX as the entry points.
  • Fx as the entry points

Project Communication

  • #torch-mlir channel on the LLVM Discord - this is the most active communication channel
  • Github issues here
  • torch-mlir section of LLVM Discourse

Install torch-mlir snapshot

At the time of writing, we release pre-built snapshots of torch-mlir for Python 3.11 and Python 3.10.

If you have supported Python version, the following commands initialize a virtual environment.

python3.11 -m venv mlir_venv
source mlir_venv/bin/activate

Or, if you want to switch over multiple versions of Python using conda, you can create a conda environment with Python 3.11.

conda create -n torch-mlir python=3.11
conda activate torch-mlir
python -m pip install --upgrade pip

Then, we can install torch-mlir with the corresponding torch and torchvision nightlies.

pip install --pre torch-mlir torchvision \
  --extra-index-url https://download.pytorch.org/whl/nightly/cpu \
  -f https://github.com/llvm/torch-mlir-release/releases/expanded_assets/dev-wheels

Using torch-mlir

Torch-MLIR is primarily a project that is integrated into compilers to bridge them to PyTorch and ONNX. If contemplating a new integration, it may be helpful to refer to existing downstreams:

While most of the project is exercised via testing paths, there are some ways that an end user can directly use the APIs without further integration:

FxImporter ResNet18

# Get the latest example if you haven't checked out the code
wget https://raw.githubusercontent.com/llvm/torch-mlir/main/projects/pt1/examples/fximporter_resnet18.py

# Run ResNet18 as a standalone script.
python projects/pt1/examples/fximporter_resnet18.py

# Output
load image from https://upload.wikimedia.org/wikipedia/commons/2/26/YellowLabradorLooking_new.jpg
...
PyTorch prediction
[('Labrador retriever', 70.65674591064453), ('golden retriever', 4.988346099853516), ('Saluki, gazelle hound', 4.477451324462891)]
torch-mlir prediction
[('Labrador retriever', 70.6567153930664), ('golden retriever', 4.988325119018555), ('Saluki, gazelle hound', 4.477458477020264)]

Repository Layout

The project follows the conventions of typical MLIR-based projects:

  • include/torch-mlir, lib structure for C++ MLIR compiler dialects/passes.
  • test for holding test code.
  • tools for torch-mlir-opt and such.
  • python top level directory for Python code

Developers

If you would like to develop and build torch-mlir from source please look at Development Notes