wip: interprocedural alias analysis #93
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ianatol
reviewed
Feb 9, 2022
| @@ -540,25 +540,139 @@ isaliased(x::Union{Argument,SSAValue}, y::Union{Argument,SSAValue}, estate::Esca | |||
| isaliased(xidx::Int, yidx::Int, estate::EscapeState) = | |||
| in_same_set(estate.aliasset, xidx, yidx) | |||
|
|
|||
| struct ArgEscapeInfo | |||
| EscapeBits::UInt8 | |||
| struct InterEscapeInfo | |||
There was a problem hiding this comment.
It feels like there should be a way for us to re-use code from EscapeInfo (and similarly for InterIndexableFields and friends) here, but maybe not possible with how subtyping is currently supported, and ultimately not super important
aviatesk
force-pushed
the
avi/interalias
branch
4 times, most recently
from
2ed12c5 to
ba7fde0
Compare
aviatesk
force-pushed
the
avi/interalias
branch
from
ba7fde0 to
98f4331
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 should improve the accuracy of our IPO analysis very much, at the cost of introducing new level of complexities.