Skip to content

Do not use as const with Z3 due to soundness issue#9011

Open
tautschnig wants to merge 3 commits into
diffblue:developfrom
tautschnig:z3-workaround
Open

Do not use as const with Z3 due to soundness issue#9011
tautschnig wants to merge 3 commits into
diffblue:developfrom
tautschnig:z3-workaround

Conversation

@tautschnig
Copy link
Copy Markdown
Collaborator

Disable as const for Z3 as it produces wrong results per Z3Prover/z3#9550.

  • 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.

Copilot AI review requested due to automatic review settings May 19, 2026 08:07
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Disables the SMT2 as const array constant construct for the Z3 backend due to a soundness bug in Z3 (Z3Prover/z3#9550) that causes incorrect results.

Changes:

  • Set use_as_const = false for the Z3 solver path in smt2_convt's constructor.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 19, 2026

Codecov Report

❌ Patch coverage is 70.83333% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.59%. Comparing base (cbdcf13) to head (63acd97).

Files with missing lines Patch % Lines
src/solvers/smt2/smt2_conv.cpp 70.83% 7 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #9011      +/-   ##
===========================================
- Coverage    80.60%   80.59%   -0.01%     
===========================================
  Files         1711     1711              
  Lines       189454   189472      +18     
  Branches        73       73              
===========================================
- Hits        152712   152710       -2     
- Misses       36742    36762      +20     

☔ 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.

@rod-chapman
Copy link
Copy Markdown
Collaborator

mlkem-native test results using patched CBMC (and standard Z3 4.15.3) look good. No regressions. A bit slower at K=4, but not too bad. A bit faster for K=2 and K=3.

@rod-chapman
Copy link
Copy Markdown
Collaborator

mldsa-native test results using patched CBMC (and standard Z3 4.15.3) look good. No regressions. A bit faster too for all parameter sets.

@rod-chapman
Copy link
Copy Markdown
Collaborator

I have re-built and re-tested the latest commit on this branch for all parameter set of mlkem-native and mldsa-native. All results are good. Please proceed.

tautschnig and others added 3 commits May 28, 2026 07:49
The DATA_INVARIANT in parse_literal for root-obj expressions
required the third element (Z3's 1-based real-root index) to be
exactly "1".  This is overly restrictive: Z3 chooses any of the
polynomial's real roots based on the model it builds, and the
chosen root depends on solver state.

Concretely, the previous commit on this branch switches Z3 from
'as const' to 'lambda' for array constants.  That input change is
sufficient to make Z3 pick a different model in
regression/cbmc/real-irrational1, where Z3 now returns

  (root-obj (+ (^ x 2) (- 2)) 2)

(the second real root of x^2-2 = 0, i.e. +sqrt(2)) instead of
index 1 (-sqrt(2)).  CBMC then aborts on the invariant.

The result of parsing a root-obj does not depend on the index:
algebraic_numbert stores only the polynomial coefficients, not
which root is chosen, so the constructed constant_exprt is the
same for every index of the same polynomial.  Drop the index
constraint and document the rationale in the comment above the
invariant.

Without this change, regression/cbmc/real-irrational1/test.desc
fails on the Z3 backend in CI.

Co-authored-by: Kiro <kiro-agent@users.noreply.github.com>
The unflatten() function reconstructs an SMT-array from a bit-vector
by storing each element. It previously required `(as const T)` to
build the base constant array, which is unavailable when use_as_const
is disabled (as done for Z3 in the next commit due to a soundness
issue). Replace with a lambda expression `(lambda ((idx T)) elem0)`
that produces the same constant-array value without `as const`.

Since Z3 rejects `get-value` on terms containing lambdas, also
switch from `define-fun` to `declare-fun` + `assert` for SSA
symbol definitions when `use_as_const` is false. This makes the
symbol opaque to `get-value` while preserving the same logical
constraint.

Co-authored-by: Kiro <kiro-agent@users.noreply.github.com>
Disable `as const` for Z3 as it produces wrong results per
Z3Prover/z3#9550.
@kroening
Copy link
Copy Markdown
Collaborator

  1. Are lambda expressions standard? If not, we'd need a use_lambda flag.

  2. Do we have a path to reenabling as const for Z3 in the future? Say could be a comment to remind us. Or we'll wait until SMT-LIB 3?

@rod-chapman
Copy link
Copy Markdown
Collaborator

Let's assume that Z3 fixes the underlying soundness problem, and we eventually adopt Z3 4.17.0. Will we revert this fix and go back to "as const" at that point?

convert_type(array_type);
out << ") ";
}
else
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I missed that use_lambda_for_array is true here. Add a comment, or better a DATA_INVARIANT.

}
else if(!use_as_const)
{
// When `as const` is unavailable, unflatten may emit lambda
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This may affect solvers that aren't Z3. This needs another branch.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants