Extend DecomposeConvolutionToLowerDimOpsPass (#17069)

Updates `DecomposeConvolutionToLowerDimOpsPass` so that when a
convolution Op is decomposed, the lowering config attribute is updated
("decomposed") accordingly. This change leverages the fact that we know
which dimension is being "removed" when the decomposition happens. The
corresponding dim/size is simply deleted when updating the lowering
config.

With the logic added in this PR, we are making sure that
`DecomposeConvolutionToLowerDimOpsPass` will no longer "drop" the
lowering config. This is beneficial - it removes the need to restore the
tiling config (for e.g. the vectoriser) from the loop nest.

BEFORE `DecomposeConvolutionToLowerDimOpsPass`:
```mlir
  #config = #iree_codegen.lowering_config<tile_sizes = [[0, 0, 0, 0, 0, 0], [1, 1, 1, 4, 0, 0], [0, 0, 0, 0, 1, 4], [0, 0, 0, 0, 0, 0]]>
  linalg.depthwise_conv_2d_nhwc_hwc lowering_config = #config
```

AFTER `DecomposeConvolutionToLowerDimOpsPass` _without_ this change:
```mlir
   linalg.depthwise_conv_1d_nwc_wc
```

AFTER `DecomposeConvolutionToLowerDimOpsPass` _with_ this change:
```mlir
   #config = #iree_codegen.lowering_config<tile_sizes = [[0, 0, 0, 0], [1, 1, 4, 0], [0, 0, 0, 1], [0, 0, 0, 0]]>
   linalg.depthwise_conv_1d_nwc_wc lowering_config = #config
```

ATM, the logic implemented here is limited to deptwhise HWC
convolutions. It can easily be extended to other Convs when that's
required.

For simplicity, it is also assumed that there's only one Conv Op per
function. This seems like the most common case. Adding support for
multiple conv ops per function is left as a TODO. It shouldn't be too
difficult to implement - it will require building a map of all
convs/lowering configs.
6 files changed
tree: e035dd33654de32bbf7fe3772ca7f1e96c27c6bf
  1. .devcontainer/
  2. .github/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. lib/
  9. llvm-external-projects/
  10. runtime/
  11. samples/
  12. tests/
  13. third_party/
  14. tools/
  15. .bazel_to_cmake.cfg.py
  16. .bazelignore
  17. .bazelrc
  18. .bazelversion
  19. .clang-format
  20. .dockerignore
  21. .git-blame-ignore-revs
  22. .gitignore
  23. .gitmodules
  24. .yamllint.yml
  25. AUTHORS
  26. BUILD.bazel
  27. CITATION.cff
  28. CMakeLists.txt
  29. configure_bazel.py
  30. CONTRIBUTING.md
  31. LICENSE
  32. MAINTAINERS.md
  33. README.md
  34. RELEASING.md
  35. 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 IREE Discord 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

License

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