LoopOptTutorial: Basic loop optimization template [STEP3] - #3
Open
etiotto wants to merge 12 commits into
Open
Conversation
…out code to update dominator tree in a member function.
… point in the predecessor of the cloned loop.
…ffs as small as possible.
… apply for step3.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
For the previous step take a look at #2.
In this step we add the code that does the actual transformation (e.g generates the LLVM IR). We start by cloning the candidate loop we have identified in the previous step, and inject the cloned loop into the LLVM IR. After adding the new loop to the LLVM IR we modify the bounds of the cloned loop and of the original loop so that the clone loop traverses the first half of the original loop iteration space and the original loop traverses the second half.