Google Git
Sign in
opensecura / 3p / openxla / iree / 77ac727c7f6cbe32ca8972b8c69bd32cba17b690
commit77ac727c7f6cbe32ca8972b8c69bd32cba17b690[log] [tgz]
authorBen Vanik <ben.vanik@gmail.com>Wed May 31 18:42:47 2023 -0700
committerGitHub <noreply@github.com>Wed May 31 18:42:47 2023 -0700
treeadbeb7e5d8df6556d696a48d99ce7622bc36ab4f
parent950e172ff9d64e87ccd06e9855dda78ddda1dd1b [diff]
Adding iree-stream-verify-async-access-ranges pass. (#13876)

This does some basic verification that AsyncAccessOpInterface ops (like
stream.async.copy and stream.async.dispatch) are in-bounds. Currently
only doing static verification but in the future it can be extended to
use relational verification (start < end, etc).

Prints useful errors like:
```
../iree-tmp/gpt2-64-stream-emplace.mlir:1603:12: error: 'stream.async.dispatch' op has invalid Read access range [180224 to 376832 for 196608] of resource %177 with size 196608; end > resource size
```

Hopefully we never produce programs like this but while iterating on
passes I've done it a few times and it's really hard to track down
(usually only via painful runtime debugging of intermediate values).
9 files changed
tree: adbeb7e5d8df6556d696a48d99ce7622bc36ab4f
  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.