First steps towards a Proof-of-Concept for analyzing threadpools #1180
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.
Since we constantly talk about it (today again in Munich), and I started thinking about it on the subway, I spent a few minutes implementing a Proof-of-Concept of the first part of an analysis:
In it's current state it can determine that
pthread_join
has been called for all members of an array, by lugging around a boolean and employing the partitioned array domain.The other piece that is missing is an analysis that shows that all created threads of a given abstract thread id is indeed contained in the array.
After we have this, we would be able to handle thread pools of constant size.
This is not meant to be merged, but as a simple Proof-of-Concept that anyone is free to adopt and develop into a proper analysis.