Symbolically propagate assertions inside a basic block #266
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 not going to be merged soon (if ever), it's just a demonstration of #258.
Assertion constraints are propagated backwards inside each basic block, with the ultimate goal of putting them at the start of the block. If this will be achieved, the checking phase will only involve checking them, and the analysis phase will never see them (unless
--assume-assert
is on).In the process, many assertions (60% on average) are simply resolved, and many more can be resolved with more sophisticated propagation - for example, tracking cells as if they were registers, or using general expression instead of only registers and constants.
Ideally we'll simply use a constraint language instead of ebpf-specific assertions, and then implement symbolic simplification and join operations, but that would be even a larger change.