-
Notifications
You must be signed in to change notification settings - Fork 76
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
Fixpoints not being reached #153
Comments
It seems like this is an issue with the |
Could it be that this is also the fault of Because it seems weird that the difference is in |
Yes, could be. It only happens with |
This is weird. I just locally tried all of them under the The log for those from SV-COMP preruns also has a weird like:
That seems to indicate there is no problem. |
I can reproduce it, also with the latest commits on master:
I think the message with The difference is Solver computed:
RHS:
|
I can run the same command (with relative paths changed) and get a different result:
This is bizarre, I don't have any uncommited changes and have made a clean build. |
Strange indeed, after going back to an older commit and another Was the release maybe dirty? |
I don't think it was because I always made the archive build on our Ubuntu 20.04 server where I didn't do any development and also did it after |
Can you reproduce it with the binary that we submitted? |
I will try that soon. It would be quite impossible to debug and fix it though if it somehow doesn't happen on new builds. it might be a hint in itself as to where the issue is. Like maybe somewhere physical equality |
I tried with the exact executable from the verifier archive (SHA-256 below) and I still gives the
|
Can you try with
Or maybe it is the GCC version or something?
|
Hmm yeah, it does happen with In the supposedly final results (linked in Slack) there's one more case: |
After merging 0f9f068/ pull #249 this also applies to |
SV-Comp '21 revealed a few example programs where we do not reach the fixpoint:
The text was updated successfully, but these errors were encountered: