Document building CBMC with IPASIR and Riss

[thomasspriggs]

So that users can do manual builds of this combination to try out
different solvers.

• Each commit message has a non-empty body, explaining why the change was made.
• Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
• The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
• Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
• My commit message includes data points confirming performance improvements (if claimed).
• My PR is restricted to a single feature or bugfix.
• White-space or formatting changes outside the feature-related changed lines are in commits of their own.

[tautschnig]

Looks good to me, but @nmanthey may wish to take a look as well.

[nmanthey]

The documentation looks good to me. Riss and its IPASIR backend did not move much in the recent past, so it's more stable.

You could hint at other solvers that support the same interface, as demonstrated by the incremental track of SAT competitions, e.g. https://satcompetition.github.io/2020/results.html

[codecov]

Codecov Report

Merging #6031 (9305563) into develop (eea16dd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #6031   +/-   ##
========================================
  Coverage    74.11%   74.11%           
========================================
  Files         1444     1444           
  Lines       157389   157389           
========================================
  Hits        116646   116646           
  Misses       40743    40743           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5601657...9305563. Read the comment docs.

[thomasspriggs]

The documentation looks good to me. Riss and its IPASIR backend did not move much in the recent past, so it's more stable.

Thanks for the review.

You could hint at other solvers that support the same interface, as demonstrated by the incremental track of SAT competitions, e.g. https://satcompetition.github.io/2020/results.html

I have plans to document building with the other solvers which also support the IPASIR interface next. I started with Riss because we currently build with Riss in one of our CI jobs.