The Torch-MLIR project aims to provide first class support from the PyTorch ecosystem to the MLIR ecosystem.
 
 
 
 
 
 
Go to file
Sambhav Jain 6e485574e5
[Pipeline] Use dedicated simplification pipeline for TorchDynamo frontend (#3376)
Discord Thread:
https://discord.com/channels/636084430946959380/1238330633328005243

## Context: 

[This](https://github.com/llvm/torch-mlir/blob/main/python/torch_mlir/fx.py#L61)
was updated to support e2e tests for the TorchDynamo frontend in
Torch-MLIR, where we run FX decompositions and import the FX IR to
generate Torch dialect, followed by
`torch-function-to-torch-backend-pipeline`, skipping only the shape/type
refinement for now. However, we should be able to skip many of the torch
simplification passes, as depicted in the [frontend
roadmap](https://github.com/llvm/torch-mlir/blob/main/docs/images/roadmap_frontend.png).

Based on IREE's TorchDynamo
[pipeline](https://github.com/iree-org/iree/blob/main/compiler/plugins/input/Torch/InputConversion/Passes.cpp#L29),
the only two passes we seem to require are: `ReduceOpVariantsPass` and
`DecomposeComplexOpsPass`. This is inline with our findings as well
based on initial exploration.

This PR creates a dedicated frontend simplification pipeline for
TorchDynamo / FX Importer which calls only `ReduceOpVariantsPass` and
`DecomposeComplexOpsPass`. We rely on the e2e fx_importer tests to
ensure we're not regressing by removing many of the passes that were
historically needed for TorchScript.

One notable change here is that we do not call the
`LowerToBackendContractPass` anymore, which used to call
`TorchSimplificationPipeline` iteratively until VerifyBackendContract
was clean. Some of this was required for the shape/type refinement to
converge, which seems a non-issue for Dynamo frontend. Do we anticipate
this (the iterative invocation of TorchSimplificationPipeline followed
by VerifyBackendContract) to be worth retaining in the Dynamo frontend
pipeline? If so, I can make those changes, PLMK.
2024-05-22 05:23:18 -07:00
.github Enable post commit run of pre-commit hooks over all files. (#3245) 2024-04-27 14:24:52 -07:00
build_tools [Release Builds] Use `-no-build-isolation` to decouple from `pyproject.toml` (#3266) 2024-04-30 00:55:25 -07:00
docs [Documentation] Show faster build command first in docs/development.md (#3355) 2024-05-17 18:59:51 +00:00
externals [torch-mlir] bump to llvm@70e227a404e51f9248c7ad5d79953805b2afacb4 (#3335) 2024-05-13 14:52:25 -07:00
include [Pipeline] Use dedicated simplification pipeline for TorchDynamo frontend (#3376) 2024-05-22 05:23:18 -07:00
lib [Pipeline] Use dedicated simplification pipeline for TorchDynamo frontend (#3376) 2024-05-22 05:23:18 -07:00
projects [FxImporter] Fix failed e2e case (#3365) 2024-05-22 00:20:54 +08:00
python [Pipeline] Use dedicated simplification pipeline for TorchDynamo frontend (#3376) 2024-05-22 05:23:18 -07:00
test [torch-mlir][sparse] replace xavier with ones initialization (#3374) 2024-05-21 17:12:55 -07:00
tools Re-organize project structure to separate PyTorch dependencies from core project. (#2542) 2023-11-02 19:45:55 -07:00
utils/bazel [Bazel] Add SparseTensorDialect deps (#3357) 2024-05-16 21:44:46 -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 Integrate llvm-project at dabdec1001dc368373dd581cf72f37a440873ce3 (#3300) 2024-05-08 14:43:06 -04:00
LICENSE Dual license the torch-mlir project. 2021-10-01 10:46:08 -07:00
README.md [FxImporter] Add an e2e test example for FxImporter (#3331) 2024-05-14 00:45:19 +08: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 (#3291) 2024-05-10 21:45:06 +05:30
pytorch-requirements.txt build: manually update PyTorch version (#3291) 2024-05-10 21:45:06 +05:30
requirements.txt python: separate build- and test-related pip dependencies (#1874) 2023-02-13 21:22:09 -06:00
setup.py [NFC reformat] Applies pre-commit formatting to Python files. (#3244) 2024-04-27 14:16:31 -07:00
test-requirements.txt [ci] Fix mpmath 1.4.0 error by forcing 1.3.0 (#2946) 2024-02-23 13:13:54 -08:00
torchvision-requirements.txt build: manually update PyTorch version (#3291) 2024-05-10 21:45:06 +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.

Simplified Architecture Diagram for README

  • TorchScript This is the most tested path down to Torch MLIR Dialect.
  • LazyTensorCore Read more details here.
  • We also have basic TorchDynamo/PyTorch 2.0 support, see our long-term roadmap and Thoughts on PyTorch 2.0 for more details.

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

Meetings

Community Meeting / Developer Hour:

  • 1st and 3rd Monday of the month at 9 am PST
  • 2nd and 4th Monday of the month at 5 pm PST

Office Hours:

  • Every Thursday at 8:30 am PST

Meeting links can be found here.

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
pip install torch-mlir -f https://github.com/llvm/torch-mlir-release/releases/expanded_assets/dev-wheels

Demos

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)]

TorchScript ResNet18

Standalone script to Convert a PyTorch ResNet18 model to MLIR and run it on the CPU Backend:

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

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

load image from https://upload.wikimedia.org/wikipedia/commons/2/26/YellowLabradorLooking_new.jpg
Downloading: "https://download.pytorch.org/models/resnet18-f37072fd.pth" to /home/mlir/.cache/torch/hub/checkpoints/resnet18-f37072fd.pth
100.0%
PyTorch prediction
[('Labrador retriever', 70.66319274902344), ('golden retriever', 4.956596374511719), ('Chesapeake Bay retriever', 4.195662975311279)]
torch-mlir prediction
[('Labrador retriever', 70.66320037841797), ('golden retriever', 4.956601619720459), ('Chesapeake Bay retriever', 4.195651531219482)]

Lazy Tensor Core

View examples here.

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