-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proof backends confuse uninterpreted constants with similar names #568
Closed
Labels
type: bug
Issues reporting bugs or unexpected/unwanted behavior
Comments
brianhuffman
added
the
type: bug
Issues reporting bugs or unexpected/unwanted behavior
label
Oct 17, 2019
brianhuffman
pushed a commit
to GaloisInc/saw-core
that referenced
this issue
Oct 18, 2019
brianhuffman
pushed a commit
to GaloisInc/saw-core
that referenced
this issue
Oct 18, 2019
Add unique VarIndex to all scConstant terms (GaloisInc/saw-script#568).
brianhuffman
pushed a commit
that referenced
this issue
Oct 18, 2019
brianhuffman
pushed a commit
that referenced
this issue
Oct 18, 2019
brianhuffman
pushed a commit
that referenced
this issue
Oct 18, 2019
Merged
Ptival
pushed a commit
that referenced
this issue
Oct 31, 2019
Ptival
pushed a commit
that referenced
this issue
Oct 31, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If we define two constants with the same name (either by local definitions or by importing from more than one Cryptol module) the
unint
proof backends get confused and assume that they are the same constant.For example, both of the
prove_print
commands in the following saw-script print "Valid":Apparently both the
sbv
andwhat4
proof backends identify uninterpreted constants by their base names alone; we should additionally use unique ids to tell them apart. (CurrentlyscConstant
terms don't contain a unique id other than the one used for hash consing, which is actually optional. We should add aVarIndex
to eachscConstant
like we do forExtCns
terms.)The text was updated successfully, but these errors were encountered: