Remove early skip of unused GV causing worklist ordering differences #6233
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.
Early skip of unused GV caused worklist ordering differences, which could result in differently ordered allocas, which is causing optimization regressions in backend.
Reverting this part of prior change (f80b8d6) from PR #5259, since it was not required for the original purpose of removing dead GVs from the staticGVs set.
Unfortunately, it is proving prohibitively difficult to craft a minimal repro for a test case that demonstrates the difference.