Repository navigation
Incremental SMT2: fix nested array address scaling - #9284
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 and
peterschrammel
as code owners
October 28, 2026 11:05
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.
lower_address_of_array_index rewrites &a[i] to (T*)&a + i, reusing the pointer type of the enclosing address_of expression. For nested arrays like int a[3][4], the inner &a[1] was given type int* (from the outer &a[1][2]), making +1 scale by sizeof(int) = 4 instead of sizeof(int[4]) = 16. Fix: derive the pointer type from the array element type, so that &a[1] gets type int(*)[4] and pointer arithmetic uses the correct stride. When the derived type differs from the original, insert a typecast to keep enclosing expression types consistent. Also move lower_address_of_array_index before the pointer size map scan so that any new pointer base types (e.g. int[4]) are registered. The C front end rewrites addresses to byte offsets before they reach the decision procedure, so the default configuration is not affected. The bug affects other IR producers that keep nested index expressions inside address_of. Reported by Jeroen Robben (https://reports.robben.io/methodology/). Fixes diffblue#9363 Co-authored-by: Kiro <kiro-agent@users.noreply.github.com>
tautschnig
force-pushed
the
kiro/rr-2-33-incr-smt2-nested-array-addr
branch
from
October 28, 2026 11:39
cf84466 to
9e4a9fe
Compare
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.
lower_address_of_array_index rewrites &a[i] to (T*)&a + i, reusing
the pointer type of the enclosing address_of expression. For nested
arrays like int a[3][4], the inner &a[1] was given type int* (from
the outer &a[1][2]), making +1 scale by sizeof(int) = 4 instead of
sizeof(int[4]) = 16.
Fix: derive the pointer type from the array element type, so that
&a[1] gets type int(*)[4] and pointer arithmetic uses the correct
stride. When the derived type differs from the original, insert a
typecast to keep enclosing expression types consistent.
Also move lower_address_of_array_index before the pointer size map
scan so that any new pointer base types (e.g. int[4]) are registered.
The C front end rewrites addresses to byte offsets before they reach
the decision procedure, so the default configuration is not affected.
The bug affects other IR producers that keep nested index expressions
inside address_of.
Fixes #9363
Found by Jeroen Robben's specification-conformance pipeline (https://reports.robben.io/methodology/).