Google Git
Sign in
opensecura / 3p / openxla / iree / 8ea1e2301660bba9f9425876002ba24351017980
commit8ea1e2301660bba9f9425876002ba24351017980[log] [tgz]
authorMax191 <44243577+Max191@users.noreply.github.com>Thu Aug 01 09:57:10 2024 -0700
committerGitHub <noreply@github.com>Thu Aug 01 12:57:10 2024 -0400
treed162f73f231d33a96aa32a7d9ea78d85eaeb3a2a
parent8f0909c3d794248ad82eafb5edcd7c3b57782476 [diff]
[DT] Move SetEncoding from GlobalOptimization to Flow (#18054)

This PR moves `SetEncoding` from `GlobalOptimization` to `Flow`, and
adds a new flag in Flow passes to run SetEncoding after dispatch region
formation. This is a step towards better handling of fusions with data
tiling. The flags for data tiling are now:

- `--iree-opt-data-tiling` still handles data tiling at global
optimization level.
- `--iree-flow-experimental-data-tiling` to enable data tiling at Flow level. To
use this path you also need to set `--iree-opt-data-tiling=false`, since
it is true by default.

`--iree-flow-experimental-data-tiling` also gets its own flag to set
`pad-factor`, `--iree-flow-pad-factor`. Use this flag when experimenting
with different pad factors for data tiling at Flow level.

The logic for `SetEncoding` stays the same with this PR, although it is
now a FunctionOpInterface pass.

---------

Signed-off-by: Max Dawkins <max.dawkins@gmail.com>
15 files changed
tree: d162f73f231d33a96aa32a7d9ea78d85eaeb3a2a
  1. .github/
  2. build_tools/
  3. compiler/
  4. docs/
  5. experimental/
  6. integrations/
  7. lib/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazel_to_cmake.cfg.py
  15. .bazelignore
  16. .bazelrc
  17. .bazelversion
  18. .clang-format
  19. .dockerignore
  20. .git-blame-ignore-revs
  21. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. .pre-commit-config.yaml
  25. .yamllint.yml
  26. AUTHORS
  27. BUILD.bazel
  28. CITATION.cff
  29. CMakeLists.txt
  30. configure_bazel.py
  31. CONTRIBUTING.md
  32. LICENSE
  33. MAINTAINERS.md
  34. README.md
  35. RELEASING.md
  36. 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

Community meeting recordings: IREE YouTube channel

  • 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.