Conservative alias analysis rules for CallFunction/CallMethod #21087
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.
Stack from ghstack:
Summary: Uses the analyzeCustomOp rule (renamed analyzeConservative)
to support CallFunction, assuming we do not know the function implementation.
When we have a know function target, and a way to summarize alias info
we can make the analysis more accurate.
Cleans up seemingly dead code in alias analysis and fixes a bug in
analyzeCustomOp where inputs are not marked as potentially aliasing the
wildcard set.
Test Plan: test_jit.py
Differential Revision: D15542512