Adding `--iree-vulkan-experimental-indirect-bindings=true` flag. (#14977)

This makes all descriptor set layouts have the new `Indirect` bit set
and plumbs it all the way through to the runtime
`IREE_HAL_DESCRIPTOR_SET_LAYOUT_FLAG_INDIRECT` bit. SPIR-V codegen can
inspect the pipeline layout attr of exports to discover which descriptor
sets are indirect and lower via `VK_KHR_buffer_device_address` and for
the runtime to specially handle the indirect descriptor sets by
producing device address buffers. The flag is currently experimental as
interop with non-indirect dispatches (custom/produced by other higher
layers like IREE input dialects/plugins) and multi-versioning (producing
both direct and indirect) are TBD. It should be sufficient for users
targeting specific Vulkan devices where they know the support is
present, though.

Note that while this is just the plumbing for the flag and the
IR/runtime bits nothing is either lowering differently or setting up the
appropriate runtime structures but it should allow codegen to start
experimenting with alternative lowerings.

Progress on #13945.
11 files changed
tree: c096453667d1a887d522423e76b923d1d32e62a7
  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

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.