-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Brodes/guard flow parsing k #17933
Closed
Closed
Brodes/guard flow parsing k #17933
Changes from 1 commit
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
aaf3ce2
Adding test cases for boolean flow.
bdrodes 40a6786
Adding expected false positive conditions for MissingCheckScanf once …
bdrodes bb989ba
Addingg expected file for test changes for MissingCheckScanf before c…
bdrodes ddfbb08
IRGuard overhaul to parse conditions using GVN.
bdrodes 0795bcc
Updating expected files for new IRGuard changes.
bdrodes d17dee5
Updating IRGuards.qll getDerivedInstruction. Always get the deriving …
bdrodes 6f17460
Revert "Updating IRGuards.qll getDerivedInstruction. Always get the d…
bdrodes 41e7dae
getDerivedInstruction uses getSourceValue()
bdrodes a18f87d
Sketch for handling k values not defined at the guard location.
bdrodes 934cf4c
Recurse to find a k
bdrodes 7498c05
Simplifying k parsing.
bdrodes 418b113
Adding conversions to the getDerivedInstruction predicate. Changed al…
bdrodes b29814e
Merge branch 'brodes/guard_flow_parsing' into brodes/guard_flow_parsi…
bdrodes 2cda23b
Removing uses of ConstantInstruction in favor of Instruction for GVN-…
bdrodes 2dfa029
Misc. poc updates to address performance issues with wireshark.
bdrodes 72dc990
Merge branch 'brodes/guard_flow_parsing' into brodes/guard_flow_parsi…
bdrodes 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.
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.
Watch out with materializing all
Instruction
s when all we really care about is the value number. If we instead change thei
parameter to be aValueNumber
instead this predicate will be a lot smaller.Note that this will require changing all the callers so that they convert the argument to a value number. You can define an (inline) helper predicate to do that conversion for you. This will keep all callers as-is, and still avoid unnecessary materialization
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 point, but what about inlining int_value instead?
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.
You can't inline it since it's recursive, unfortunately.
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.
Ah true true. The inline helper function I think is the winner then, which is basically the best of both worlds.