fix(ssa): Unused functions removals post folding constant Brillig calls #7265
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.
Description
Problem*
Silly bug leftover from #7260, but also fixes this removal pass to be more accurate. We are not checking the full new call graph of unused functions.
e.g. for the following SSA:
After constant folding we would still have:
even though it would be unused. This is because we would only inline Brillig calls for ACIR entry points. Thus, we would still have a call to f2, even though f1 is now unused, thus f2 is also unused.
Summary*
I simply moved to using our pre-existing
remove_unreachable_functions
pass. I felt this kept a better separation of concerns for the passes and was a more complete removal of unreachable functions.Additional Context
Documentation*
Check one:
PR Checklist*
cargo fmt
on default settings.