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

MathSAT crashes because we use bvadd with three parameters #185

Open
Heizmann opened this issue May 24, 2017 · 4 comments
Open

MathSAT crashes because we use bvadd with three parameters #185

Heizmann opened this issue May 24, 2017 · 4 comments
Assignees

Comments

@Heizmann
Copy link
Member

Separate ticket for one issue of #150 .
The SMT solver MathSAT crashes because we use bvadd with three parameters, which is not legal according to the SMT-LIB standard.
The number of paramters is deeply integrated in our SMT library. We want to use bvadd with three parameters because

  1. more conveniant and Z3 and CVC4 support it
  2. interpolants genereated by Z3 contain bvadd with more than two parameters

(The function bvadd with more than two parameters does not occur that often in practice, since we construct affine terms that summarize literals also for bitvectors.)

Heizmann added a commit that referenced this issue May 24, 2017
…_SOLVER_COMPLAINS to TraceCheckReasonUnknown. Translate solver crash because of bvadd with three arguments to response unknown
Heizmann added a commit that referenced this issue May 24, 2017
@danieldietsch
Copy link
Member

Is this the issue we talked about (solutions: add required bvadd definitions during C translation OR allow backtranslation to introduce additional boogie functions) or something else?

@Heizmann
Copy link
Member Author

Heizmann commented Jun 2, 2017

No, is a different issue.

@Heizmann
Copy link
Member Author

Thanks to Alberto Griggio, MathSAT support bvadd with multiple parameters. So for MathSAT the problem is gone.
The problem will however arise again if we use another solver or if we want to submit standard compliant SMT-LIB benchmarks.

@danieldietsch
Copy link
Member

@Heizmann: Then lets keep this ticket around as reminder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants