Google Git
Sign in
opensecura / 3p / openxla / iree / 40258db63fdfd2228adb2fd0baaea53b9e3c9d63
commit40258db63fdfd2228adb2fd0baaea53b9e3c9d63[log] [tgz]
authorHan-Chung Wang <hanhan0912@gmail.com>Fri Aug 16 11:01:44 2024 -0700
committerGitHub <noreply@github.com>Fri Aug 16 11:01:44 2024 -0700
tree04a08f405f28a3b8985ae172117cece4dbd025c8
parentd25712c84d741baf1ba8e4ebeeb6151eb34df4d6 [diff]
[CodeGen][DT] Make the TypeConverter carry targetAttr info. (#18242)

The revision adds `ExecutableTargetAttr` the
MaterializeEncodingTypeConverter's data member; updates the
MaterializeEncodingFn function to take an additional
`ExecutableTargetAttr`. The type converter should know what the target
device it. This mostly changes ABI, so there are no changes on lit
tests.

It was not done in this way because we wanted to upstream Encoding
dialect when we're developing data-tiling. We tried to decouple the deps
between Encoding and IREE hard. However, there are IREE specifics in the
encodings, so we end up with collapsing them into IREE main source tree.
Given that the type converter needs all target attribute details (to
figure out the best option for materialization), the revision makes the
change; removes one level of nesting logics in the setup. I.e., the
`getMaterializeEncodingFn` wrapper function is removed.

This revisions also applies the cleanups. The type converter has an
additional function to query encoding info. Instead of passing private
`MaterializeEncodingFn` data member, it now passes the whole type
converter to the helper functions in materialization patterns. Because
the type converter has the all information, and it is more structurally.

Signed-off-by: hanhanW <hanhan0912@gmail.com>
5 files changed
tree: 04a08f405f28a3b8985ae172117cece4dbd025c8
  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.

IREE Discord Status pre-commit OpenSSF Best Practices

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

Release status

PackageRelease status
GitHub release (stable)GitHub Release
GitHub release (nightly)GitHub Release
Python iree-compilerPyPI version
Python iree-runtimePyPI version

Build status

CI PkgCI

Host platformBuild status
LinuxCI - Linux x64 clang
CI - Linux arm64 clang
macOSCI - macOS x64 clang
WindowsCI - Windows x64 MSVC

For the full list of workflows see https://iree.dev/developers/general/github-actions/.

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.