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

SMTChecker: Upgrade CVC4 to cvc5 and switch from API to SMT-LIB2 interface #15078

Merged
merged 3 commits into from
Jun 11, 2024

Commits on Jun 11, 2024

  1. SMTChecker: Upgrade CVC4 to cvc5

    Instead of compiling `solc` itself with CVC4 support, it is now enough
    to have `cvc5` executable on PATH when running the compiler.
    Instead of using API of CVC4, we now use SMT-LIB2 interface.
    That means we write the queries to temporary SMT-LIB2 files and call
    the solver process directly to run on the file.
    blishko committed Jun 11, 2024
    Configuration menu
    Copy the full SHA
    b8ba5da View commit details
    Browse the repository at this point in the history
  2. Update CI images

    blishko committed Jun 11, 2024
    Configuration menu
    Copy the full SHA
    025f9a2 View commit details
    Browse the repository at this point in the history
  3. SMTChecker: Allow using multiple external solvers in one analysis

    We are using SMTCommand inside UniversalCallback to call external
    solvers on queries produced my our engines.
    
    Previous mechanism set the external solver once during initialization
    and it was not possible to change it later. This meant, that it would
    not be possible to use, e.g., Eldarica and cvc5 at the same time.
    
    Here we move the proper setup for SMTCommand just before we call it.
    This setup is customized by subclasses of (CHC)SmtLib2Interface, which
    call corresponding external solvers.
    blishko committed Jun 11, 2024
    Configuration menu
    Copy the full SHA
    20ae0f2 View commit details
    Browse the repository at this point in the history