-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dataflow: Simplify references to access paths from prior stage. #18258
Merged
aschackmull
merged 14 commits into
github:main
from
aschackmull:dataflow/simplify-apapprox3
Dec 11, 2024
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
c8046fa
Dataflow: Drop some ApApprox columns and joins.
aschackmull 7c888eb
Dataflow: Replace some allowsFieldFlow,apa pairs with emptyAp boolean.
aschackmull d404406
Dataflow: Remove ApApprox column in out-flow.
aschackmull 262f64f
Dataflow: Remove unused columns.
aschackmull 882a985
Dataflow: Remove useless join.
aschackmull a77adad
Dataflow: Remove more unused columns.
aschackmull 22e0636
Dataflow: Insert a few getApprox calls to remove even more columns.
aschackmull 501cbda
Dataflow: Remove another ApApprox join and related columns.
aschackmull 231bf9d
Dataflow: Drop ApApprox join in fwdFlowStore.
aschackmull 4e155f8
Dataflow: Insert a few getApprox calls to remove ApApprox from fwdFlow.
aschackmull 40f7713
Dataflow: Minor simplification.
aschackmull da17970
Java: Accept expected file changes.
aschackmull d6a4080
Dataflow: Address review comment.
aschackmull cac131d
Dataflow: Rename a couple of predicates.
aschackmull File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these test changes expected?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. When a callable has both flow-through and flow to a sink without flow-through and the difference is dependent on the access path (and not just if it is empty or not), then we generate slightly more nodes, since we can no longer determine with the same level of precision whether we need to remember a summary context or not. To pinpoint it in the code, this is due to the change to
PrevStage::parameterMayFlowThrough
using anemptyAp
boolean instead ofApApprox
in its use incallEdgeArgParamRestricted
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to know that this is expected.