[stream] Switch to perform tight packing of sub-byte elements (#13344)

Thus far, for sub-byte element types, we unconditionally expand
them to byte-aligned ones. It wastes storage and memory. This
becomes more difficult with recent large language models, where
we have a large amount of data for weights.

Thus, this commit starts to perform tight packing of sub-byte
elements at the stream level. With this, sub-byte element types
can flow down the compilation pipeline, allowing each backend to
handle it accordingly.

Given handling of sub-byte elements are tricky, right now we only
enable selected sub-byte element types that is some power of two
to get started. Other cases can be enabled when we have the use
case.

Progress towards https://github.com/openxla/iree/issues/12859
16 files changed
tree: 64ff1fecd28be5a654aa55502d05f17fa1de17c2
  1. .devcontainer/
  2. .github/
  3. benchmarks/
  4. build_tools/
  5. compiler/
  6. docs/
  7. experimental/
  8. integrations/
  9. lib/
  10. llvm-external-projects/
  11. runtime/
  12. samples/
  13. tests/
  14. third_party/
  15. tools/
  16. .bazel_to_cmake.cfg.py
  17. .bazelignore
  18. .bazelrc
  19. .bazelversion
  20. .clang-format
  21. .dockerignore
  22. .gitignore
  23. .gitmodules
  24. .pylintrc
  25. .style.yapf
  26. .yamllint.yml
  27. AUTHORS
  28. BUILD.bazel
  29. CITATION.cff
  30. CMakeLists.txt
  31. configure_bazel.py
  32. CONTRIBUTING.md
  33. LICENSE
  34. README.md
  35. 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.