-
Notifications
You must be signed in to change notification settings - Fork 274
No need to track write set with temporary variables #6327
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
feliperodri
commented
Sep 2, 2021
- 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.
daa3c6d
to
3f8c767
Compare
Codecov Report
@@ Coverage Diff @@
## develop #6327 +/- ##
===========================================
- Coverage 75.91% 75.90% -0.01%
===========================================
Files 1514 1514
Lines 163984 163942 -42
===========================================
- Hits 124485 124442 -43
- Misses 39499 39500 +1
Continue to review full report at Codecov.
|
3f8c767
to
9e73175
Compare
No need to track write set with temporary variables. This also avoids reporting NULL dereferences when users adds targets that might be NULL in the assigns clause. Signed-off-by: Felipe R. Monteiro <[email protected]>
Signed-off-by: Felipe R. Monteiro <[email protected]>
Avoid escaping unnecessary characters. Signed-off-by: Felipe R. Monteiro <[email protected]>
Signed-off-by: Felipe R. Monteiro <[email protected]>
17983dc
to
43f0f89
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.
LGTM 👍
Thanks!