Google Git
Sign in
opensecura / 3p / openxla / iree / 5da8c71abb15ec556d14fe388c53c48b9defe637
commit5da8c71abb15ec556d14fe388c53c48b9defe637[log] [tgz]
authorScott Todd <scotttodd@google.com>Tue Jun 06 11:31:09 2023 -0700
committerGitHub <noreply@github.com>Tue Jun 06 11:31:09 2023 -0700
treeb6a21ab186b3eb9862b22440a4144e9d78f772e6
parent18a1bac40e049075567b6500a3c81f95eca57052 [diff]
Add `iree-stream-resource-alias-mutable-bindings` flag. (#13965)

This pass option is currently necessary to run some WebGPU programs
correctly, so this adds a compiler flag to set it. Without the option, I
see errors like
```
Writable storage buffer binding aliasing found between [BindGroup] set at bind group index 0, binding index 0, and [BindGroup] set at bind group index 0, binding index 2, with overlapping ranges (offset: 0, size: 256) and (offset: 0, size: 256) in [Buffer].
 - While encoding [ComputePassEncoder].DispatchWorkgroups(1, 5, 1).
 
[Invalid CommandBuffer] is invalid.
    at ValidateObject (../../third_party/dawn/src/dawn/native/Device.cpp:689)
    at ValidateSubmit (../../third_party/dawn/src/dawn/native/Queue.cpp:442)
```

We can't enable the option by default yet, since it causes some severe
performance regressions on CUDA:
https://github.com/openxla/iree/pull/13323. The tests also have a few
suspicious TODOs, but I want to unblock correctness testing on WebGPU
before digging in deeper.
8 files changed
tree: b6a21ab186b3eb9862b22440a4144e9d78f772e6
  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.