Google Git
Sign in
opensecura / 3p / openxla / iree / e6d6c39fef33943e671dedefd9ab324cea16b828
commite6d6c39fef33943e671dedefd9ab324cea16b828[log] [tgz]
authorScott Todd <scotttodd@google.com>Wed Jun 21 11:30:47 2023 -0700
committerGitHub <noreply@github.com>Wed Jun 21 11:30:47 2023 -0700
treed70fa679e20657289bdc05d2c11e9fb1f899e907
parent39d45a1c4ab68cc0ab21f55d5d8b470178c54468 [diff]
Add diagrams to ml-frameworks website pages. (#14145)

Diagrams are a nice way to break up the flow of a webpage and
communicate relationships visually. This "ml-frameworks" pages
(https://openxla.github.io/iree/guides/ml-frameworks/) already uses
sections, icons, and lists, but I want to keep making the website easier
to scan through, as we bridge between so many different technologies.


![image](https://github.com/openxla/iree/assets/4010439/7e31fe15-ce7d-46b1-84e9-53885ded20e2)

![image](https://github.com/openxla/iree/assets/4010439/b2d690c5-ff35-47f5-a8b6-6b6daa156a25)

![image](https://github.com/openxla/iree/assets/4010439/aee56bfa-d15a-4085-88fc-85f0410662ef)

![image](https://github.com/openxla/iree/assets/4010439/279ea730-89ac-4527-9700-b0241b724020)

---

I also tried a version of this diagram with more detail, but the layout
was tricky to tune:

![image](https://github.com/openxla/iree/assets/4010439/bbd58a8d-4c52-421c-b21d-032bcd4043f1)
5 files changed
tree: d70fa679e20657289bdc05d2c11e9fb1f899e907
  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. .gitignore
  22. .gitmodules
  23. .pylintrc
  24. .style.yapf
  25. .yamllint.yml
  26. AUTHORS
  27. BUILD.bazel
  28. CITATION.cff
  29. CMakeLists.txt
  30. configure_bazel.py
  31. CONTRIBUTING.md
  32. LICENSE
  33. README.md
  34. 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.