[MLIR][OpenMP] Independent omp.loop_nest translation #247
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
This patch refactors the process of translating loop wrappers and `omp.loop_nest` operations so that both are independent. This makes all these loop-related operations be handled using the same process, instead of the previous approach where `omp.loop_nest`s were handled directly as part of their associated loop wrappers. In order to still have access to the collapsed loop CanonicalLoopInfo information while translating loop wrappers, this is stored globally in a stack-like container.
|
PR stack:
It has been checked to pass Lit and smoke-fort tests. |
|
Replaced by an internal PR. |
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.
This patch refactors the process of translating loop wrappers and
omp.loop_nestoperations so that both are independent. This makes all these loop-related operations be handled using the same process, instead of the previous approach whereomp.loop_nests were handled directly as part of their associated loop wrappers.In order to still have access to the collapsed loop CanonicalLoopInfo information while translating loop wrappers, this is stored globally in a stack-like container.