Collapse `linalg.generic` (#11295)

PR implements collapsing `linalg.generic`. It first identifies the
collapsible parallel dimensions and collapses them all. It does
collapsing on the shapes rather than loops. Therefore, it does not
introduce any arithmetic to calculate loop indices and etc. When there
are `reduction` it can still collapse `parallel` loops but it does not
mix them.

It finds the longest same sequence in each `AffineMap`. There can be
multiple. For example, for the following case it is `d1, d3, d0`. Here
the `d1, d3, d0` loops are not nested; there are other loop(s) in
between. But they're all parallel loops, so it's safe to interchange
them out. After interchanging, it is also safe to collapse them.

```
indexing_maps = [affine_map<(d0, d1, d2, d3, d4) -> (d1, d3, d0)>, 
                 affine_map<(d0, d1, d2, d3, d4) -> (d2, d1, d3, d0, d4)>]
```
After collapsing, iree can parallelize more dimensions of the
`linalg.generic`, this yields significant performance improvement.

Current limitations:
1. Dynamic tensor shapes: Generating `tensor.expand_shape` with dynamic
tensors is ambiguous. It is a known limitation of MLIR. It is possible
to solve that. See RFC:
https://discourse.llvm.org/t/rfc-add-explicit-shape-inputs-to-tensor-expand-shape/65952

2. Non-contiguous loops. Current mechanism does collapsing on tensor
shapes, not on the loops. If there is non-contiguous loops (like
transpose), collapsing tensor would change behavior. #11385 tackles this
problem by linearizing the workgroup id. Alternative idea is to
linearize loops.
9 files changed
tree: 03b8db440fad12b8504215cad042c5ce7d99bf48
  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.