Swift: initial interprocedural data flow implementation #9342
Conversation
This file contains hidden or 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
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| } | ||
|
|
||
| override DataFlowCallable getEnclosingCallable() { isParameterOf(result, _) } |
Check warning
Code scanning / CodeQL
Using implicit `this`
MathiasVP
previously approved these changes
May 27, 2022
swift/ql/lib/codeql/swift/dataflow/internal/DataFlowDispatch.qll
Outdated
Show resolved
Hide resolved
swift/ql/lib/codeql/swift/dataflow/internal/DataFlowDispatch.qll
Outdated
Show resolved
Hide resolved
swift/ql/lib/codeql/swift/dataflow/internal/DataFlowPrivate.qll
Outdated
Show resolved
Hide resolved
MathiasVP
force-pushed
the
rdmarsh2/swift/dataflow-global-flow
branch
from
bc83757 to
ef31aec
Compare
MathiasVP
approved these changes
May 30, 2022
hvitved
reviewed
Aug 3, 2022
| } | ||
| } | ||
|
|
||
| private predicate localFlowSsaInput(Node nodeFrom, Ssa::Definition def, Ssa::Definition next) { |
There was a problem hiding this comment.
I think this predicate deserves a comment, probably just the same as for the Ruby version.
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.
Most of this PR is fairly straightforward pairings of input and output nodes, plus the addition of flow steps for Phi nodes. The main subtlety is the way functions are modeled in the call graph - there's now a non-AST control flow node for each function with the parameter declarations and body as children. The reason these aren't
AstControlFlowNodes is so that nested functions don't appear in the CFG of their containing function and result in duplicated nodes.