Skip to content
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

Support multiple solvers for double-checking #118

Closed
atomb opened this issue Oct 2, 2014 · 1 comment
Closed

Support multiple solvers for double-checking #118

atomb opened this issue Oct 2, 2014 · 1 comment
Labels
feature request Asking for new or improved functionality wontfix For issues that we've reviewed and decided do not require changes.
Milestone

Comments

@atomb
Copy link
Contributor

atomb commented Oct 2, 2014

This is a bifurcation of #7, since it covered multiple tasks. It would be nice to run all supported solvers to attempt to prove a property, and then check their results against one another for compatibility. Results of "unknown" or "error" would be compatible with any other result, but "sat" and "unsat" would be incompatible. Multiple "unsat" results would be compatible. Multiple "sat" results could use the approach proposed for allsat, returning a list of satisfying assignments.

@atomb atomb added this to the Cryptol 2.2 milestone Oct 2, 2014
@kiniry kiniry added the feature request Asking for new or improved functionality label Dec 2, 2014
@kiniry kiniry modified the milestone: Cryptol 2.2 Dec 2, 2014
@dylanmc
Copy link
Contributor

dylanmc commented Mar 8, 2016

:set prover=any comes close to this, but doesn't do the cross-checking.

@acfoltzer acfoltzer added this to the Someday milestone Jun 29, 2016
@atomb atomb added the wontfix For issues that we've reviewed and decided do not require changes. label Jan 29, 2021
@atomb atomb closed this as completed Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Asking for new or improved functionality wontfix For issues that we've reviewed and decided do not require changes.
Projects
None yet
Development

No branches or pull requests

4 participants