-
Notifications
You must be signed in to change notification settings - Fork 285
Speed up dafny verify by reducing memory pressure
#5827
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
Speed up dafny verify by reducing memory pressure
#5827
Conversation
…boardDrummer/dafny into onlyClaimVerificationMemoryPerModule
…boardDrummer/dafny into onlyClaimVerificationMemoryPerModule
| new("--progress", "While verifying, output information that helps track progress") { | ||
| IsHidden = true | ||
| }; | ||
| public enum ProgressLevel { None, Symbol, SymbolParts } |
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.
Can the help text document the difference between the levels?
| Related message: loop invariant violation | ||
| Iterators.dfy(470,4): Error: possible violation of yield-ensures condition | ||
| Iterators.dfy(451,21): Related location: this proposition could not be proved | ||
| Iterators.dfy(251,9): Error: decreases clause might not decrease |
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.
Why did the ordering change? Seems like a regression since we've been better about keeping these in order lately.
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.
It's unavoidable, since we want to verify one module at a time to be able to release memory after verifying that module. When nested modules occur, the contents of different modules can be intertwined.
method A
module Nested {
method B
}
method CWe can do A,C,B or B,A,C, but we can no longer do A,B,C if we verify entire modules at a time.
…onMemoryPerModule
Description
dafny verifyHow has this been tested?
dafny verify, and confirmed that Boogie programs are no longer kept in memory after they've been verifiedBy submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.