-
Notifications
You must be signed in to change notification settings - Fork 274
Flattening of ID_nondet_symbol for unbounded arrays [blocks: #3619] #4016
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✔️
Passed Diffblue compatibility checks (cbmc commit: 915bb93).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99326800
Marking do-not-merge until explicitly approved by @romainbrenguier or anyone else via a TG test run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving as part of an approved PR
915bb93
to
e2a7181
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚫
This PR failed Diffblue compatibility checks (cbmc commit: e2a7181).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99415339
Status will be re-evaluated on next push.
Please contact @peterschrammel, @thk123, or @allredj for support.
Common spurious failures:
- the cbmc commit has disappeared in the mean time (e.g. in a force-push)
- the author is not in the list of contributors (e.g. first-time contributors).
The incompatibility may have been introduced by an earlier PR. In that case merging this
PR should be avoided unless it fixes the current incompatibility.
@romainbrenguier confirmed that this passes TG tests. |
e2a7181
to
808b212
Compare
symbol_exprt and nondet_symbol_exprt are to be treated the same when in comes to the back-end: they both introduce an uninterpreted, nullary function. Note the difference at the level of symbolic execution/programs, where the value of symbols may change (while the value of nondet_symbol_exprts cannot).
808b212
to
909a29e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✔️
Passed Diffblue compatibility checks (cbmc commit: 909a29e).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99575614
symbol_exprt and nondet_symbol_exprt are to be treated the same when in comes to
the back-end: they both introduce an uninterpreted, nullary function. Note the
difference at the level of symbolic execution/programs, where the value of
symbols may change (while the value of nondet_symbol_exprts cannot).
This is factored out from #3619 to make it easier to pinpoint what exactly causes trouble with TG. The commit is exactly the same as the first one from #3619, which has been approved already.