Revert "Stop propagating/inlining string constants (#6234)" #6258
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 reverts commit 9090ce5.
Disallowing such optimization prevents e.g.
string.eqfrom beingoptimized out, if doing so depended on propagating constants to its arms.
Instead, to fix the real problem here, #6257 adds a pass that is run at the
end to collect
string.constto globals. What will happen in practice is thatwe propagate strings as we optimize, then at the end we collect them.
cc @gkdn - do you have thoughts on what order should these PRs land?