| commit | 05ce39f3fba4b5cc6eee18a431f8f8e16fa9b5d2 | [log] [tgz] |
|---|---|---|
| author | Han-Chung Wang <hanhan0912@gmail.com> | Mon Dec 16 02:12:26 2024 -0800 |
| committer | GitHub <noreply@github.com> | Mon Dec 16 10:12:26 2024 +0000 |
| tree | cd74cc88db74e82c9172a2b4742f3c08236dee96 | |
| parent | 67a05a45aec34d779bc7ff8968bd1c93133a037c [diff] |
[DT] Unify encoding materialization pass into a single pass. (#19454) The revision creates a generic materialization pass and uses it for backends that implement data-tiling. After months of development, we identify that the needs of GPU is a superset of the needs of CPU. To be more specific, it has the additional "swizzle" field in terms of layout. It means that the GPU set_encoding/unset_encoding lowering patterns cover the needs of CPU path. The lowering of contraction ops is different. CPU lowers it to mmt4d op, while GPU lowers it to multi_mma op. However, the lowering of contraction is implemented through attribute interface. Thus, we can have a generic pattern to lower contraction ops. To make the review process much easier, the revision is created by 5 commits. 1. It directly creates the MaterializeEncoding pass and copy-paste the GPU patterns: SetEncodingOpLoweringConversion, UnSetEncodingOpLoweringConversion, and MaterializeContractionOp. In the first commit, it also updates the GPU tests to use the new pass. 2. The GPU data-tiling does not support element-wise generic op lowering atm. The second commit moves the pattern to shared pattern set and bail out when swizzle is present. This is an NFC for both pipelines. 3. The third commit replaces the existing materialization pass with the generic pass, and deletes all the legacy passes. 4. The four commit moves the lit tests from `Common/[CPU|GPU]/test` to `Common/test`. 5. Now there are duplicate patterns for set_encoding, unset_encoding, and contraction ops lowering. The last commit deletes the legacy patterns, and move the patterns from MaterializeEncoding.cpp to where the legacy patterns locate. Furthermore, it renames the file as `MaterializeEncodingPatterns.cpp`. The revision retains the MaterializeEncodingIntoNop pass, and add a TODO item. Because it is still used by MaterializeHomogeneousEncoding pass. It can be deleted once we deprecate the early materialization path. --------- Signed-off-by: hanhanW <hanhan0912@gmail.com>
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 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
| Package | Release status |
|---|---|
| GitHub release (stable) |  |
| GitHub release (nightly) |  |
| Python iree-base-compiler |  |
| Python iree-base-runtime |  |
| Host platform | Build status |
|---|---|
| Linux |   |
| macOS |  |
| Windows |  |
For the full list of workflows see https://iree.dev/developers/general/github-actions/.
See our website for more information.
Community meeting recordings: IREE YouTube channel
IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.