-
Notifications
You must be signed in to change notification settings - Fork 273
GOTO trace: no timestamps for single-threaded programs #7403
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
Conversation
bb11492
to
ed8700e
Compare
Codecov ReportBase: 78.39% // Head: 78.40% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #7403 +/- ##
========================================
Coverage 78.39% 78.40%
========================================
Files 1655 1655
Lines 190281 190275 -6
========================================
+ Hits 149172 149178 +6
+ Misses 41109 41097 -12
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I am happy to see updates to the trace building such that the calls it makes to the decision procedure are more consistent. However it looks like the changes to I haven't done an in-depth review of this PR yet, this is just an initial comment. |
I noticed the same when looking at #7404 - I'm more than happy for #7404 to land first, and I'll rebase this one on top of it. |
ed8700e
to
4289b5e
Compare
Rebased. |
Avoid reading clock values when those won't be known to the solver as single-threaded source programs do not have partial-order constraints. Other back-ends were silent about this, but the incremental SMT back-end produced warnings (which the user could do nothing about).
4289b5e
to
f1a830b
Compare
Avoid reading clock values when those won't be known to the solver as single-threaded source programs do not have partial-order constraints. Other back-ends were silent about this, but the incremental SMT back-end produced warnings (which the user could do nothing about).