[5.3] SIL: fix memory behavior of global_addr for globals with non-fixed layout. #31231
Conversation
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
…yout. Global variables with resilient types might be allocated into a buffer and not statically in the data segment. In this case, the global_addr depends on alloc_global being executed first. We model this by letting global_addr have a side effect. It prevents e.g. LICM to move a global_addr out of a loop while keeping the alloc_global inside the loop. rdar://problem/61602640
Mark as executable test
eeckstein
changed the title
|
@swift-ci test |
AnthonyLatsis
added
swift 5.3
🍒 release cherry pick
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.
Global variables with resilient types might be allocated into a buffer and not statically in the data segment.
In this case, the global_addr depends on alloc_global being executed first.
Letting global_addr have a side effect ensures that this dependency is kept.
It prevents e.g. LICM to move a global_addr out of a loop while keeping the alloc_global inside the loop.
This is a cherry-pick of #31205 and #31228
rdar://problem/61602640