-
Notifications
You must be signed in to change notification settings - Fork 53
Add bitwuzla #332
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
Add bitwuzla #332
Conversation
…r array index and element type getter
…for a term, if there is not, its not a constant)
…recise in Bitwuzla and use convertValue for constants)
…terms/sorts etc. are shared) and fix pop bug
… tests not based on integers here!)
…sary C code and use it in the formula manager (TODO: proper temporary files in the C wrapper)
…documentation in the wrapper
…pport concurrent contexts, not stacks)
…ethods and extend it for Bitwuzla
…substitute variables w bound variables, but this changes existing terms!
…s or declarations
…now, not variables that are named after the number....) Note: Bitwuzla does not accept real numbers in scientific notation for FPs
…lues ourselfs, which fails, and will always fail in Java (I reported that we need a function to get the decimal value of a FP in Bitwuzla to the devs)
…nd add the correct options for unsat core and unsat core w assumptions
Bitwuzla has several critical issues that need to be resolved before it can be merged:
There are also minor issues that can be resolved later:
|
@kfriedberger could you review the model, especially the ValueAssignments for UFs and Arrays for me please? I would like some feedback for my implementation. |
It seems like trivial Boolean based formulas are rewritten/simplified by Bitwuzla even if the option |
Update on the symbol naming: if there is a space in a symbol name, we expect that the symbol name will be wrapped in |
…s enum values from the implementation and may break again when we update Bitwuzla. We should use SWIG to auto-generate this code.
…t what result is expected here.
… (and our variable cache).
…b version that is too old for the solver. Compare with 886529b.
…ist (e.g. because of parsing)
…or missing categories
…1 (mostly parsing the same variable twice now returns 2 distinct variables)
I've opened a new discussion about our issues with the parser on the Bitwuzla bugtracker: |
I've published the new version 0.3.1 and updated our code for it. We should update the CI and then we can merge. |
…The solver can't parse this and we may have to handle it on our side.
Formulas in the new version of Bitwutzla just released are now capable of being used thread independently. |
…A_KIND_BV_SMOD in BitwuzlaFormulaCreator.getDeclarationKind.
No description provided.