Use tbaa_immut for getfield of immutable types #13286
Merged
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
|
Ref #8867 and this is master (post-codegen-rewrite) only. |
|
Ping. Is this OK to merge? |
yuyichao
added a commit
that referenced
this pull request
Sep 28, 2015
Use tbaa_immut for getfield of immutable types
Closed
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 fixes a vectorization regression in this script
LLVM refuses to vectorize it on the current master because it cannot prove that the array doesn't alias the fields of
factor::Complex64. (seetest-0.4.llandtest-master.llin the same directory for the raw llvmir including tbaa info)@simonster @vtjnash