-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Spacer: Timeout with simple array example #7425
Comments
Looks like Eldarica 2.1 can solve this example (~12 seconds wall clock time on my machine). |
@blishko. Thanks for the hint. That is true. Also on my machine Eldarica is able to solve the benchmark. However, originally I was aiming for a slight modification of the benchmark above: FYI. Here is the mentioned variation of the benchmark:
|
It seems to me you need a quantified invariant here in order to be inductive. |
@blishko. Thanks a lot for your pointers. I really appreciate it! I will give FreqHorn a try. |
FYI: I tried freqhorn. It manages to solve the first benchmark almost instantly. However, for the second, only slightly more complex benchmark, it returns |
Hi everyone,
I am trying to use Spacer to verify programs that contain arrays/maps, when I noticed for some seemingly simple benchmarks Spacer gets stuck in a loop. Using different parameters for spacer and z3 did not help. I distilled a minimal simple benchmark that Spacer struggles with. Is there anything I can do get an answer for this and similar benchmarks (like combination of special parameters, different encoding, custom invariants, ...)?
The benchmark encodes the following transition system: The state consists of an array (called
set
) and integer (calledelement
).set
is initialized to be an array mapping every integer tofalse
, andelement
to0
. There is a single (symbolic) transition incrementingelement
(set
remains the same). The query is given by the property thatselect set element
is false, which must hold asset
is always the array mapping every integer tofalse
.Any help is appreciated!
The text was updated successfully, but these errors were encountered: