[mir-opt] Improve SimplifyLocals pass so it can remove unused consts #65624
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.
The
ConstProp
can cause many locals to be initialized to a constantvalue and then never read from.
ConstProp
can also evaluate ZSTs intoconstant values. Previously, many of these would be removed by other
parts of the MIR optimization pipeline. However, evaluating ZSTs
(especially
()
) into constant values defeated those parts of theoptimizer and so in a2e3ed5, I added a
hack to
ConstProp
that skips evaluating ZSTs to avoid that regression.This commit changes
SimplifyLocals
so that it doesn't consider writesof const values to a local to be a use of that local. In doing so,
SimplifyLocals
is able to remove otherwise unused locals left behindby other optimization passes (
ConstProp
in particular).r? @oli-obk