Avoid generating cell-fragments during execution #2253
Merged
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
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 PR makes it possible to generate specifications parseable by the KEVM specification from Kontrol (or subexecutions of KEVM): runtimeverification/kontrol#262
The use of cell fragments is removed by storing entire cells. This means that intermediate states generated by symbolically executing KEVM contain no cell fragments, which was stopping them from being parseable by the K inner-parser for rules/claims. Because of this, some generated KCFGs could not be verified for correctness (when turning the KCFG basic blocks into K claims).
This is pulled out of this PR: #2241