Google Git
Sign in
opensecura / 3p / openxla / iree / 3bd115aac2e753a629ebf95ebd54057b8a3a0fe6
commit3bd115aac2e753a629ebf95ebd54057b8a3a0fe6[log] [tgz]
authorScott Todd <scotttodd@google.com>Fri Jun 09 08:49:23 2023 -0700
committerGitHub <noreply@github.com>Fri Jun 09 08:49:23 2023 -0700
treeb0ec5148abd69015fb8310ee5ba2bd26226b19b9
parentc12bf50e92d78d6203fda255f3b47cb0000728b8 [diff]
Refresh deployment-configuration website pages. (#14013)

I started to write a new "compiler tips" page, then I found better
places to put those tips within the pages that already exist. While I
added the new sections, I proofread the pages and refreshed their
structure and style.

(I still plan on adding new pages in this "guides" section)

|  | |
|--------|--------|
| Current section |
https://openxla.github.io/iree/guides/deployment-configurations |
| Preview of this PR |
https://scotttodd.github.io/iree/guides/deployment-configurations |

High level changes:

* Add icon prefixes to many sections
* Adjust grammar / phrasing
* Format tables and code blocks
* Remove `--iree-input-type=stablehlo` (auto should work, and TF /
StableHLO are not the focus of these pages)
* Add sample `iree-run-module --list_drivers` and `iree-compile
--iree-hal-list-target-backends` output
* Call Metal "experimental" and not "stale"
* Add tip for "--iree-llvmcpu-target-cpu-features"
5 files changed
tree: b0ec5148abd69015fb8310ee5ba2bd26226b19b9
  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.