[GlobalOptimization] Add pattern to reassociate dequantization + matmul `linalg.gen… (#15278)

…eric` ops

Dequantization ops that are consumed by matmuls are currently only fused
into a dispatch region, but we can do even better by reassociating these
fused operations (see https://github.com/openxla/iree/issues/14951).

It is important to note that this pattern does affect precision, and is
a trade off between precision and performance. It is set to opt-in with
`--iree-global-opt-enable-quantized-matmul-reassociation`

This pattern rewrites a sequence of dequantization->matmul
`linalg.generic` ops into a new sequence of `linalg.generic` ops. The
new sequence of ops is as follows:

1. A sequence of `linalg.generic` ops that dynamically quantize the
non-quantized input to the matmul. This is very cheap in skinny matmul
cases, where the non-quantized input is small compared to the quantized
input.
2. A `linalg.generic` op that performs an integer matmul. This is the
key performance optimization here. On CPU, we want to be doing integer
matmuls where we can, but the matmul needs to be picked up by a
VectorContractCustomKernel for now. Eventually it will be better to
rewrite to `linalg.matmul` here to target ukernels.
3. A final `linalg.generic` op that performs the dequantization scale
and zero point math, as well as performing the remaining reduction of
the matmul. The matmul from 2. only reduces within quantized groups,
while this op does the reduction across groups.

This also moves the FuseDequantizationMatmul pass to GlobalOptimization
17 files changed
tree: 356a85a329e85b09e939bfbc17c33e1b949c5132
  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.