[Metaschedule] MultiLevelTiling for wide vector architectures #12845
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@tvm-bot rerun |
vinx13
approved these changes
Sep 20, 2022
xinetzone
pushed a commit
to daobook/tvm
that referenced
this pull request
Nov 25, 2022
…#12845) * [Metaschedule] Introduce MultiLevelTiling for wide vector architecture * update test * format * cpplint
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In
MultiLevelTiling, the size of the loop that is going to be vectorized is completely random. This is not a good fit for backends with wide vector registers such as Hexagon.This PR introduces an extension of
MultiLevelTiling, to effectively utilize wide vectors. The loop over the innermost spatial axis of the output buffer is always vectorized with the maximum vector length. This makes it possible to auto schedule for Hexagon successfully.cc @vinx13 @junrushao