-
Notifications
You must be signed in to change notification settings - Fork 273
Patch set for SV-COMP'19 [depends-on: #2000, #3462] #3486
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A proper fix would be done via #354
Check whether the object part of a pointer is greater or equal the total number of objects, or equals a dynamic object that has not actually been allocated on a given trace.
Benchmarks not including headers files fail as we only provided a definition of __builtin_alloca, which alloca expands to in standard libary headers, but none for alloca directly.
Iterating over all expression tress has considerable performance cost, seemingly accounting for up to 10% of runtime (on SV-COMP benchmarks, with profiling enabled).
This reduces the memory footprint by two pointers for both named_sub and comments. The cost is that computing the size of lists and add/remove require additional iterator increments.
On SV-COMP benchmarks, hashing accounts for >22% of CPU time (with profiling enabled).
This is used by pthread-divine/tls_basic_true-unreach-call in SV-COMP.
As we internally use dynamic allocation, we previously did not distinguish alloca-allocated from malloc/calloc-allocated ones.
They are too expensive due to extensive shared-variable use.
…object With level-2 counters incremented on declaration and non-deterministic initialisation upon allocation, the only remaining sources are pointer dereferencing, where uninitialised objects necessarily refer to invalid objects. This is a cleaner implementation of 369f077. Removing only the code introduced in 369f077 would yield a wrong result for regression/cbmc/Local_out_of_scope3.
@tautschnig #2220 has been merged, so you can tick it off |
tautschnig
added a commit
that referenced
this pull request
May 8, 2019
Enable HASH_CODE by default to avoid repeated hash computation [blocks: #3486]
tautschnig
added a commit
that referenced
this pull request
May 28, 2019
Use std::forward_list instead of std::map in irept by default [blocks: #3486]
tautschnig
added a commit
that referenced
this pull request
Jan 28, 2021
Do not sort operands as part of simplification [blocks: #3486]
Closing as the remaining patches of PRs of their own. |
tautschnig
added a commit
that referenced
this pull request
May 19, 2021
Do not unnecessarily sort guard conjuncts [blocks: #3486]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just to provide a to-do list of PRs to be created or existing PRs to be merged to put in place the fixes applied for CBMC's SV-COMP'19 submission. No review needed or expected.