Repository navigation
SMT2: fix extractbit with a non-constant index - #9295
Open
tautschnig wants to merge 1 commit into
Open
tautschnig wants to merge 1 commit into
tautschnig wants to merge 1 commit into
Conversation
tautschnig
requested review from
TGWDB,
kroening,
martin-cs and
peterschrammel
as code owners
October 28, 2026 11:06
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.
For a non-constant index, extractbit(src, index) is encoded as bit 0 of src shifted right by index. The index was converted to the type of the source with a typecast_exprt, which converts the value: for a fixedbv source it scales the index by 2^fraction_bits, for a c_bool source it maps any non-zero index to 1, and for a source narrower than the index it truncates the index, so that an out-of-range index such as 256 for an 8-bit source selects bit 0. Instead, zero-extend both the source and the index to the wider of the two widths. Then an out-of-range index shifts out all bits and the result is false. (The SAT back end leaves the result unconstrained for out-of-range indices.) C programs do not produce such expressions, but other front ends do. Reported by Jeroen Robben (https://reports.robben.io/methodology/). Fixes diffblue#9367 Co-authored-by: Kiro <kiro-agent@users.noreply.github.com>
tautschnig
force-pushed
the
kiro/rr-37-extractbit-index-cast
branch
from
October 28, 2026 11:39
8863651 to
f733327
Compare
TGWDB
approved these changes
Oct 28, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For a non-constant index, extractbit(src, index) is encoded as bit 0
of src shifted right by index. The index was converted to the type of
the source with a typecast_exprt, which converts the value: for a
fixedbv source it scales the index by 2^fraction_bits, for a c_bool
source it maps any non-zero index to 1, and for a source narrower
than the index it truncates the index, so that an out-of-range index
such as 256 for an 8-bit source selects bit 0.
Instead, zero-extend both the source and the index to the wider of the
two widths. Then an out-of-range index shifts out all bits and the
result is false. (The SAT back end leaves the result unconstrained for
out-of-range indices.)
C programs do not produce such expressions, but other front ends do.
Fixes #9367
Found by Jeroen Robben's specification-conformance pipeline (https://reports.robben.io/methodology/).