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
Our race analysis can output "proofs" as success messages with allglobs enabled. This is useful for inspecting why Goblint believes the program to be correct.
We could do something similar for termination analysis: when we manage to prove a loop to be bounded and thus terminate, optionally output a success message with the bound (at least non-relationally, if not relationally). @karoliineh looked at some SV-COMP termination program where termination wasn't obvious because the loop could both increment (by 2) or decrement (by 1) the counter based on some condition.
The text was updated successfully, but these errors were encountered:
I think we had such a message at some point but then removed it to be less verbose. One can probably go dig through #1093 to find the commit where it was removed.
Our race analysis can output "proofs" as success messages with
allglobs
enabled. This is useful for inspecting why Goblint believes the program to be correct.We could do something similar for termination analysis: when we manage to prove a loop to be bounded and thus terminate, optionally output a success message with the bound (at least non-relationally, if not relationally). @karoliineh looked at some SV-COMP termination program where termination wasn't obvious because the loop could both increment (by 2) or decrement (by 1) the counter based on some condition.
The text was updated successfully, but these errors were encountered: