Google Git
Sign in
opensecura / 3p / openxla / iree / be8437f1af0fa97d4e7f3a9c74571b60988723cd
commitbe8437f1af0fa97d4e7f3a9c74571b60988723cd[log] [tgz]
authorScott Todd <scotttodd@google.com>Mon Jul 17 13:09:22 2023 -0700
committerGitHub <noreply@github.com>Mon Jul 17 13:09:22 2023 -0700
treeea7e6e1e413dade34e327bd5cd21dd6b771652b5
parent280b14bc32ec963df9796032ef0b3d7771cf2df4 [diff]
Refresh reference/bindings/ website pages. (#14380)

This updates the "API bindings" category of the website, focusing on:

* Which languages have API bindings, and which features those bindings
support
* Explaining API concepts with diagrams (docstrings -> reference pages
would be cool too: https://github.com/openxla/iree/issues/5477)
* Showing how to depend on IREE to use those APIs (the mechanics of
using shared libraries and C/C++ sources)
* **NOTE**: This is not fully finished yet, but I think it's ready to
checkpoint and publish as-is

|  | |
|--------|--------|
| Current section | https://openxla.github.io/iree/reference/bindings/ |
| Preview of this PR |
https://scotttodd.github.io/iree/reference/bindings/ |

I'm also removing the (empty) `bindings/tensorflow-lite/` page. I'm not
aware of anyone using those bindings, and the source should have enough
comments for a motivated user to find their way :crossed_fingers:
(closes https://github.com/openxla/iree/issues/5462).
9 files changed
tree: ea7e6e1e413dade34e327bd5cd21dd6b771652b5
  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

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