Google Git
Sign in
opensecura / 3p / openxla / iree / baedac1ba8ca83d2982d538b81fafaff502f8a29
commitbaedac1ba8ca83d2982d538b81fafaff502f8a29[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Fri Jan 19 11:00:43 2024 -0800
committerGitHub <noreply@github.com>Fri Jan 19 11:00:43 2024 -0800
treed154bcfb9efab04bb69197659509b7f84e5ab74b
parent65680c69ff1433129be76bf37b028521d30cc5ac [diff]
Update IREE architecture diagrams. (#16170)

Changes:

* Input dialects 'iree', 'tensor' -> 'arith', 'linalg' (Could revert
this or pick other dialects, I like anchoring on `linalg` though)
* Drop `iree-*-trace` tools (see
https://github.com/openxla/iree/pull/16134)
* Switch "Java" bindings for "Rust" (Java bindings are
old/state/unmaintained and unofficial Rust bindings exist)

Other ideas:

* Could mention modules like 'io'
(https://github.com/openxla/iree/tree/main/runtime/src/iree/modules)
* Could include more ecosystem projects in the "IREE Importers" section,
like JAX PJRT, PyTorch SHARK-Turbine, and StableHLO
* Could include more device code generation targets (AMD AIE)
* Maybe touch on AOT and JIT uses somehow

Export in dark mode was actually fine. No need to change settings beyond
the dark mode toggle.
3 files changed
tree: d154bcfb9efab04bb69197659509b7f84e5ab74b
  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. README.md
  33. 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

License

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