Add support for using PDL to replicate the functionality in MLP sample that uses Transform dialect. (#16453)

This PR adds a sample that uses PDL to match a subgraph corresponding to
MLP and replaces with a `flow.dispatch`, that invokes an external
function which is provided by a system plugin.

To enable this an new pass `--iree-preprocessing-apply-pdl-patterns` is
added that has an option to read in the PDL pattern file and applies it
to the input program.
To support this a custom rewrite function `rewriteAsFlowDispatch` is
added that takes as arguments
- the root of the matched DAG (this is replaced by the matcher)
- A list of values that represent the dynamic dimensions of the results
of the root
- The name of the external function provided by the plugin
- The operands to the external function.

What is missing is the support to specify the workload and number of
workgroups to use while invoking the external function. This could be
solved by having a custom PDL operation (if possible) that accepts the
workload and a region that computes the number of workgroups based on
the workload. For now that is not handled, and the nubmer of workgroups
is set to `{1, 1, 1}`. This is still a useful thing to
prototype/checkpoint, but for any reasonable deployment this needs to be
fixed.

This PR adds a sample that matches the input in TOSA dialect. Due to the
TOSA dialect definition, the matmul now has a batch dimension as well.
To be possible to use the same plugin implementation, the `llvm.bareptr`
calling convention is used for the external function so that the inputs
(outputs) are passed (passed by reference) using pointer, offset only,
and `memref.extract_strided_metadata` is used to extract this
information from the multi-dimensional memrefs within the dispatch.
21 files changed
tree: 083f76dc1614fbbe9d9254cc699c9ed15db2ab42
  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 IREE Discord 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.