-
Notifications
You must be signed in to change notification settings - Fork 18
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
Prove the partial correctness of a small program with a loop #91
Merged
Merged
Changes from 4 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
9626294
Prove the partial correctness of a small program with a loop
shigoel c9db156
Merge branch 'main' into add_loop_vcg
shigoel a93740d
Cosim: Print uniqueBaseName in case of a mismatch
shigoel 9654cdf
Merge branch 'main' into add_loop_vcg
shigoel da148df
Merge branch 'main' into add_loop_vcg
shigoel 950b9d5
Add missing Copyright header for Correctness/ArmSpec.lean
shigoel 3948c2d
Merge branch 'main' into add_loop_vcg
shigoel 796c414
Fix build; use genEqStepThms
shigoel 0e95f55
Merge branch 'main' into add_loop_vcg
shigoel de6f994
Merge branch 'main' into add_loop_vcg
shigoel a395bba
Use `sym_n` instead of `sym1_n`; delete old #genStepTheorems, use Tes…
shigoel 65d6660
Fix case in file names
shigoel 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
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.
Cool! I think this would be useful to have more broadly; especially since we name step-theorems according to their address in hex
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.
One reason why I'm hesitant re. this unexpander is that register indices also appear in hex then. E.g.,
StateField.GPR 0xc#5
andStateField.SFP 0xd#5
, which is inconvenient.Maybe we need more directed unexpanders...
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.
Something I've been thinking about: it might be nice to introduce a simple abbreviation for addresses and raw instructions
Then, we could somehow define the unexpanders to apply just for those types, not for all bitvectors
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, that's a good idea, regardless of the unexpander issue.
Note that it also helps to see machine components' values as hex; for instance, consider:
vs.