[HAL] Add configuration stage in executable lowerings (#15362)

The core idea behind this split is to allow for passes to be added in
between strategy selection and translation, thereby expanding and
contracting the set of variants per executable based on the known
feature requirements for those strategies.

The reason a split is needed is because strategy selection itself should
not care what other variants of the executable are being compiled,
however to deduplicate them we need to nest at the executable level.
Codegen was already partially structured to enable this (by way of
encoding the lowering pipelines as an IR attribute). This PR just
recovers the separation that was already there.

In terms of immediate benefits, this adds an option to dump executable
configurations (essentially post-kernel config dispatches) and
substitute them in, making it significantly easier to get the default
lowering configuration for a dispatch from the compiler, tweak it, and
plug it back in. Additionally benchmark dumps now happen after this
stage for the same reason.
40 files changed
tree: 705f88bb786dd5087b4a173a26c268c674e15fc0
  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.