-
Notifications
You must be signed in to change notification settings - Fork 280
Don't use symex_dynamic:: magic string in multiple places #3481
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
Don't use symex_dynamic:: magic string in multiple places #3481
Conversation
thk123
commented
Nov 30, 2018
- Each commit message has a non-empty body, explaining why the change was made.
- Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
- The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
- Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
- My commit message includes data points confirming performance improvements (if claimed).
- My PR is restricted to a single feature or bugfix.
- White-space or formatting changes outside the feature-related changed lines are in commits of their own.
src/util/simplify_expr_pointer.cpp
Outdated
@@ -9,6 +9,7 @@ Author: Daniel Kroening, [email protected] | |||
#include "simplify_expr_class.h" | |||
|
|||
#include <cassert> | |||
#include <goto-symex/goto_symex.h> |
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.
I suspect that's a bad cross-module dependency (but then, so is utils knowing about symex internal magic)
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.
Yeah looks like this particular simplification shouldn't be in util. Happy to either remove this particular usage - or pull the macro into util
?
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.
091e987
to
f455438
Compare
@tautschnig @smowton dependency comment addressed |
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.
Fine with this for now, but please make an issue to avoid non-symex modules having to know about a symex-specific magic identifier
Done in #3526 |
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: abe2102).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/93531642
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.
@tautschnig this is ready for a final review |
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.
My apologies for delaying this for such a long time. Looks good to me, but needs a rebase.
abe2102
to
10df3c0
Compare
Rebased and found another one. |
10df3c0
to
50df2a8
Compare
50df2a8
to
042ad74
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: 042ad74).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/102308171
Time to play wack-a-mole with code owners - I need a goto-instrument code owner review: |