-
Notifications
You must be signed in to change notification settings - Fork 277
Remove unused ID_free and related methods #3141
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
Remove unused ID_free and related methods #3141
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: acc15f6).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/87651924
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.
If ID_free
is really unused, then can we also take it out of the list of valid irep IDs?
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'm with @martin-cs: can we please kill any use of ID_free
? I don't mind whether done in this PR or a follow-up one and thus approving. Maybe @kroening can confirm that this is the way to go?
It appears to be impossible to create a free statement (as opposed to a call to stdlib's free); therefore these paths cannot be exercised.
acc15f6
to
35cfbb8
Compare
Updated; @kroening can you confirm if this is ok? Is there perhaps a secret out-of-tree user that creates a codet with statement == "free"? |
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: 35cfbb8).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/87744962
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.
For @kroening to confirm.
It appears to be impossible to create a free statement (as opposed to a call to stdlib's free); therefore this path can't be exercised. All the better, since updating everyone's pointers (rather than tracking allocated / deallocated status with the object itself) is surely a mistake in any case.
Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.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).White-space or formatting changes outside the feature-related changed lines are in commits of their own.