You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
brianhuffman opened this issue
Dec 23, 2015
· 0 comments
Assignees
Labels
obsoleteIssues that involve/depend on deprecated code, such that they are not worth pursuingwontfixClosed issues that we decided not to fix, but are still potentially relevant
For example: Suppose Java method foo operates on arrays of arbitrary size. We can use java_verify to prove a method override foo_thm for foo with the array size fixed at, say, 10. Then suppose that method bar calls foo with an array argument of size 5. If we run java_verify on bar, passing in foo_thm as an override, then the generated proof obligations will be ill-typed.
In the LWE proofs (e.g. revision 96bc7d74 of saw-examples) this eventually produces errors like the following when we try to run z3 via the SBV backend:
Checking final assertions
./Data/Vector/Generic.hs:400 (slice): invalid slice (90,10,10)
To fix this, java_verify should compare the types of method overrides with the array sizes in the calling context, and refuse to apply the override if the types don't match.
The text was updated successfully, but these errors were encountered:
atomb
added
obsolete
Issues that involve/depend on deprecated code, such that they are not worth pursuing
and removed
next
priority
High-priority issues
labels
Apr 2, 2019
atomb
added
the
wontfix
Closed issues that we decided not to fix, but are still potentially relevant
label
Jan 29, 2021
obsoleteIssues that involve/depend on deprecated code, such that they are not worth pursuingwontfixClosed issues that we decided not to fix, but are still potentially relevant
For example: Suppose Java method
foo
operates on arrays of arbitrary size. We can usejava_verify
to prove a method overridefoo_thm
forfoo
with the array size fixed at, say, 10. Then suppose that methodbar
callsfoo
with an array argument of size 5. If we runjava_verify
onbar
, passing infoo_thm
as an override, then the generated proof obligations will be ill-typed.In the LWE proofs (e.g. revision 96bc7d74 of saw-examples) this eventually produces errors like the following when we try to run z3 via the SBV backend:
Checking final assertions
./Data/Vector/Generic.hs:400 (slice): invalid slice (90,10,10)
To fix this,
java_verify
should compare the types of method overrides with the array sizes in the calling context, and refuse to apply the override if the types don't match.The text was updated successfully, but these errors were encountered: