[experimental] DanglingCFG analysis prototype #124133
Draft
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
usx95
force-pushed
the
lifetime-cfg
branch
7 times, most recently
from
2291706 to
4a1f461
Compare
|
✅ With the latest revision this PR passed the C/C++ code formatter. |
usx95
force-pushed
the
lifetime-cfg
branch
3 times, most recently
from
be91e32 to
fcdadc7
Compare
usx95
force-pushed
the
lifetime-cfg
branch
8 times, most recently
from
52028ae to
5f9375e
Compare
usx95
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently focussing on CFG based
return-stack-addrandstack-use-after-scopediagnostics.This analysis is primarily based on
[[gsl::Pointer]],[gsl::Owner]],[[clang::lifetimebound]], <TODO:[[clang::lifetime_capture_by(X)]]> annotations.<TODO: references are not yet tracked>
For spectators, the tests would be the most useful.