Add an example of generalized packing (#12076)

This revision demonstrates how the generalized packing transformation is
a one-size fits all implementation
for tiling linalg ops of rank N to linalg ops of higher rank.

The tensor.pack / tensor.unpack representation allows us to complete our
panoply of composable linalg transformations.
Now, one can either:
1. lower a linalg op to loops and use classical loop-based tiling
techniques (e.g. Allen&Kennedy, polyhdral/affine etc)
2. tile an N-D linalg op to N-D loops surrounding an N-D linalg op. This
often preserves the name of the linalg op and is at the basis of the
TilingInterface.
3. (this PR) tile an N-D linalg op to a 2*N-D linalg.generic. This step
requires that the tile dimensions divide the problem dimension.
tensor.pack / tensor.unpack provide this guarantee.

Step 3. can easily be adapted to produce a new named op (e.g. mmt4d)
when relevant, the point of this PR is to demonstrate generality.

This is related to discussion #12075.

An additional pattern is added to convert tensor.pack/unpack to
linalg_ext.pack/unpack until IREE adopts the upstream variants.
With this, it is possible to form dispatch regions without failing to
lower.

One thing to note in the IREE pass pipeline is that the
InterchangeGenericOps breaks the normalization property of the packing.
This can be recovered after the fact but it would be better to disable
in such cases if possible.

At this time, `iree-compile` fails on the `iree_linalg_ext` ops as it
wants statically allocated buffers to be hoisted to the top of the
function.

Both these issues can be left for a followup investigation.
7 files changed
tree: 71d9626f1764ee72a422d65a29b8d0d4c0be4a6f
  1. .github/
  2. benchmarks/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazelignore
  15. .bazelrc
  16. .bazelversion
  17. .clang-format
  18. .dockerignore
  19. .gitignore
  20. .gitmodules
  21. .pylintrc
  22. .style.yapf
  23. .yamllint.yml
  24. AUTHORS
  25. BUILD.bazel
  26. CITATION.cff
  27. CMakeLists.txt
  28. configure_bazel.py
  29. CONTRIBUTING.md
  30. LICENSE
  31. README.md
  32. WORKSPACE
README.md

IREE: Intermediate Representation Execution Environment

IREE (Intermediate Representation Execution Environment, pronounced as “eerie”) is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR that scales up to meet the needs of the datacenter and down to satisfy the constraints and special considerations of mobile and edge deployments.

See our website for project details, user guides, and instructions on building from source.

CI Status

Project Status

IREE is still in its early phase. We have settled down on the overarching infrastructure and are actively improving various software components as well as project logistics. It is still quite far from ready for everyday use and is made available without any support at the moment. With that said, we welcome any kind of feedback on any communication channels!

Communication Channels

Related Project Channels

  • MLIR topic within LLVM Discourse: IREE is enabled by and heavily relies on MLIR. IREE sometimes is referred to in certain MLIR discussions. Useful if you are also interested in MLIR evolution.

Architecture Overview

IREE Architecture IREE Architecture

See our website for more information.

Presentations and Talks

  • 2021-06-09: IREE Runtime Design Tech Talk (recording and slides)
  • 2020-08-20: IREE CodeGen: MLIR Open Design Meeting Presentation (recording and slides)
  • 2020-03-18: Interactive HAL IR Walkthrough (recording)
  • 2020-01-31: End-to-end MLIR Workflow in IREE: MLIR Open Design Meeting Presentation (recording and slides)

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.