Z3 option update#694
Merged
Merged
Conversation
Closed
This file contains hidden or 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
1 participant
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 updates the Z3 options we're using to be the same as those currently used by Dafny (see https://github.com/dafny-lang/dafny/blob/0ef835d49860fedee0fbefacd61d227abf854af6/Source/DafnyCore/DafnyOptions.cs).
This change seems to usually cause a small improvement in performance with our currently supported Z3 version (4.8.7) or no change at all; I have not seen any case where it worsened performance.
More importantly, the new options work much better with newer Z3 versions, which are borderline unusable with the options we currently use.