Skip to content

SMT2: fix for encoding of range-typed symbols#8969

Merged
tautschnig merged 1 commit intodevelopfrom
smt2-range-encoding
May 6, 2026
Merged

SMT2: fix for encoding of range-typed symbols#8969
tautschnig merged 1 commit intodevelopfrom
smt2-range-encoding

Conversation

@kroening
Copy link
Copy Markdown
Collaborator

The SMT2 backend now adds a constraint to ranged-typed symbols that prevent out-of-range values.

The SMT2 backend uses a bit-vector encoding for finite integer ranges, which uses a logarithmic number of bits in the width of the interval. If the width of the interval is not a power of two, values above the upper end of the range are possible.

  • Each commit message has a non-empty body, explaining why the change was made.
  • n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • n/a 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).
  • n/a My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.55%. Comparing base (30ca13c) to head (b9ef902).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #8969   +/-   ##
========================================
  Coverage    80.55%   80.55%           
========================================
  Files         1706     1707    +1     
  Lines       188982   189012   +30     
  Branches        73       73           
========================================
+ Hits        152227   152254   +27     
- Misses       36755    36758    +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment thread src/solvers/smt2/smt2_conv.cpp
Comment thread src/solvers/smt2/smt2_conv.cpp
@kroening kroening force-pushed the smt2-range-encoding branch 2 times, most recently from fa63d82 to 90ed521 Compare May 5, 2026 22:44
The SMT2 backend now adds a constraint to ranged-typed symbols that prevent
out-of-range values.

The SMT2 backend uses a bit-vector encoding for finite integer ranges, which
uses a logarithmic number of bits in the width of the interval.  If the
width of the interval is not a power of two, values above the upper end of
the range are possible.
@tautschnig tautschnig force-pushed the smt2-range-encoding branch from 90ed521 to b9ef902 Compare May 5, 2026 23:07
@tautschnig tautschnig merged commit 16906d1 into develop May 6, 2026
44 checks passed
@tautschnig tautschnig deleted the smt2-range-encoding branch May 6, 2026 07:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants