Fix sroa replace constant with non constant in entry block #6591
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
ReplaceConstantWithInst(C, V) replaces uses of C in the current function with V. If such a use C is an instruction I, the it replaces uses of C in I with V. However, this function did not make sure to only perform this replacement if V dominates I. As a result, it may end up replacing uses of C in instructions before the definition of V. The fix is to lazily compute the dominator tree in ReplaceConstantWithInst so that we can guard the replacement with that dominance check.
In order to replace memcpy instances, sometimes constants need to be replaced with instructions. Rather than place them wherever is immediately convenient, placing them in the entry block after the allocas ensures they have access to the allocas while making sure they dominate any uses, increasing the chances that the associated memcpy can be replaced rather than potentially introducing a domination issue that would prevent the memcpy replace.
We try to keep the allocas at the top of the entry block. This initialization code placed the init instruction just after the alloca it was initializing, which left it in the middle of the allocas. This disrupted future attempts to find the end of the allocas and potentially put instructions referencing allocas before the relevant alloca.
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.
A variation on #6556 that I'm not sure generates the right code just yet. The first commit slurps up the tests from #6556. The HLSL test passes without crashing, this change preserves the memcpy replacement so the .ll test doesn't pass. The concern is with the resulting copy seeming to be pointless.