-
Notifications
You must be signed in to change notification settings - Fork 151
Directly construct KCFGs in foundry-kompile #1377
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
Merged
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
2918836
kevm-pyk/: allow passing --depth through to kprove from kevm foundry-…
ehildenb d28e123
kevm-pyk/solc_to_k: abstract pre/post ACCOUNTS cell map rest
ehildenb da0d990
kevm-pyk/__main__: output failing proof results for foundry-prove
ehildenb e743c50
kevm-pyk/__main__: generate KCFGs directly
ehildenb 5dd219c
kevm-pyk/__main__: avoiding building spec modules at all
ehildenb 84dbb63
kevm-pyk/__main__: remove unused spec_module
ehildenb df2c267
kevm-pyk/solc_to_k: use symbol attribute to make sure klabels are unq…
ehildenb ee14377
kevm-pyk/__main__: allowing rekompiling/reiniting individually
ehildenb 2373acd
kevm-pyk/: minimize prover output by default, allow turning off
ehildenb d05cd1a
kevm-pyk/__main__: format failures from prover better
ehildenb 6237cc1
tests/foundry: update expected output
ehildenb 1a0806e
kevm-pyk/: add support for --lemma argument to foundry-prove
ehildenb 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
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
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.
What's the reason behind removing the spec module? Is it to separate the auto-generated rules from the hand-written claims?
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.
Just to reduce the output size since we aren't using the claims anymore to make the input specifications. The KCFGs are stored structurally (instead of textual claims), and then when we want to run the proof, the KCFG is written as a claim to a file for calling KProve on.