Google Git
Sign in
opensecura / 3p / openxla / iree / b339919814f10589f779b39c3ab7c6575716dab6
commitb339919814f10589f779b39c3ab7c6575716dab6[log] [tgz]
authorBen Vanik <ben.vanik@gmail.com>Fri Feb 10 21:27:35 2023 -0800
committerGitHub <noreply@github.com>Fri Feb 10 21:27:35 2023 -0800
treea8e646378b77f81b048cc267f169fb116a184df6
parente7786e5ba2cd9bb95af85f9403f3a81376137d02 [diff]
parent745e7f923952ba2a4fbef5283edcc972c9119f44 [diff]
Supporting CUDA importable buffers in compatibility check. (#12093)

Folds in the fix from https://github.com/iree-org/iree/pull/12066 in
addition to some nice textual error messages when the buffer
compatibility check fails during allocation or import.

This also fixes the aliasing of IREE_HAL_MEMORY_TYPE_HOST_LOCAL with
IREE_HAL_MEMORY_TYPE_DEVICE_LOCAL that made it impossible to
differentiate the two based solely on HOST_VISIBLE/DEVICE_VISIBLE. I
don't recall why the bits aliased and can't find the reason. It's
possible that since the compiler was never producing the values with the
bit set there was other code
compensating for this as part of the change to use OPTIMAL bits and it
went unnoticed.

In order to avoid breaking the binary format the bit is now added but
existing vmfb files should continue to work as expected.
Whenever a full breaking change is introduced we can clean up the bit
ordering in the bitfield.

Fixes #12066.
tree: a8e646378b77f81b048cc267f169fb116a184df6
  1. .github/
  2. benchmarks/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazelignore
  15. .bazelrc
  16. .bazelversion
  17. .clang-format
  18. .dockerignore
  19. .gitignore
  20. .gitmodules
  21. .pylintrc
  22. .style.yapf
  23. .yamllint.yml
  24. AUTHORS
  25. BUILD.bazel
  26. CITATION.cff
  27. CMakeLists.txt
  28. configure_bazel.py
  29. CONTRIBUTING.md
  30. LICENSE
  31. README.md
  32. 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.