Google Git
Sign in
opensecura / 3p / openxla / iree / 38ca3be9293c2dda377fbc4595c5f314bfc0a97b
commit38ca3be9293c2dda377fbc4595c5f314bfc0a97b[log] [tgz]
authorMax191 <44243577+Max191@users.noreply.github.com>Tue Jan 21 10:01:16 2025 -0500
committerGitHub <noreply@github.com>Tue Jan 21 07:01:16 2025 -0800
treefe13f7555f14078a3d0dd80d93fcb0ae503ea568
parent4a7af8728126c722d4b293af1bc8bf21b732164a [diff]
[GPU] Add SwapExpandShapeWithSlice pattern to loop fusion pass (#19729)

This PR moves the `SwapExpandShapeWithSlicePattern` to
Codegen/Common/Transforms, and adds the pattern to the
FuseAndHoistParallelLoops pass.

This pattern is generally useful for tiling fusion, because it exposes
more producer fusion opportunities when there are reshapes in the IR,
but more specifically, it is useful in combination with the pattern
introduced in https://github.com/iree-org/iree/pull/19295. That pattern
creates an expanded parallel_insert_slice, and an expand_shape on the
corresponding init block arg in the forall loop body. This makes the
slice on the init argument lower dimensional than the
parallel_insert_slice at the end. It is better for bufferization if
these slices are the same, and this pattern makes that happen by
bubbling the slice of the init arg up through the expand_shape,
increasing the dimensionality to match the parallel_insert_slice.

---------

Signed-off-by: Max Dawkins <max.dawkins@gmail.com>
7 files changed
tree: fe13f7555f14078a3d0dd80d93fcb0ae503ea568
  1. .github/
  2. build_tools/
  3. compiler/
  4. docs/
  5. experimental/
  6. integrations/
  7. lib/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazel_to_cmake.cfg.py
  15. .bazelignore
  16. .bazelrc
  17. .bazelversion
  18. .clang-format
  19. .git-blame-ignore-revs
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .pre-commit-config.yaml
  24. .yamllint.yml
  25. AUTHORS
  26. BUILD.bazel
  27. CITATION.cff
  28. CMakeLists.txt
  29. configure_bazel.py
  30. CONTRIBUTING.md
  31. LICENSE
  32. MAINTAINERS.md
  33. README.md
  34. RELEASING.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.

IREE Discord Status pre-commit OpenSSF Best Practices

Project news

Project status

Release status

Releases notes are published on GitHub releases.

PackageRelease status
GitHub release (stable)GitHub Release
GitHub release (nightly)GitHub Release
Python iree-base-compilerPyPI version
Python iree-base-runtimePyPI version

Build status

CI PkgCI

Nightly build status

Operating systemBuild status
LinuxCI - Linux arm64 clang
macOSCI - macOS x64 clang
macOSCI - macOS arm64 clang
WindowsCI - Windows x64 MSVC

For the full list of workflows see https://iree.dev/developers/general/github-actions/.

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

Community meeting recordings: IREE YouTube channel

DateTitleRecordingSlides
2021-06-09IREE Runtime Design Tech Talkrecordingslides
2020-08-20IREE CodeGen (MLIR Open Design Meeting)recordingslides
2020-03-18Interactive HAL IR Walkthroughrecording
2020-01-31End-to-end MLIR Workflow in IREE (MLIR Open Design Meeting)recordingslides

License

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