Parallel for loop vectorization legality tweak #26
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
neboat
pushed a commit
that referenced
this pull request
Dec 6, 2017
stelleg
pushed a commit
to stelleg/Tapir-LLVM
that referenced
this pull request
Dec 19, 2018
stelleg
pushed a commit
to stelleg/Tapir-LLVM
that referenced
this pull request
Dec 20, 2018
stelleg
pushed a commit
to stelleg/Tapir-LLVM
that referenced
this pull request
Dec 20, 2018
stelleg
pushed a commit
to stelleg/Tapir-LLVM
that referenced
this pull request
Jan 12, 2019
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.
Turns out LLVM LoopVectorizer already has logic dealing with loops that have been annotated as parallel (for OpenMP loops, for example?). This commit simply makes LLVM recognize Tapir/Rhino loops as parallel loops.