Repository navigation
full_slicer: do not remove ASSUME false - #9470
Open
tautschnig wants to merge 1 commit into
Open
tautschnig wants to merge 1 commit into
tautschnig wants to merge 1 commit into
Conversation
An ASSUME false has no successors in the control-flow graph, so no instruction is control dependent on it. The full slicer therefore removed it unless it was the slicing criterion, which made the instructions that follow it reachable on paths that it blocked, resulting in spurious counterexamples. For example, each failing Java assertion is encoded as ASSERT false followed by ASSUME false, so that with --full-slice any later assertion was reported as failing with the values that violate the first one. Loops unwound by goto-instrument --unwind (without unwinding assertions) and function bodies generated with --generate-function-body-options assume-false end paths the same way; in the latter case the slicer removed the call of the function. Always retain ASSUME false instructions. Their control dependencies, and the calls of the function that contains them, are then retained as well. On jbmc/regression/jbmc-strings with --full-slice this fixes 6 tests and does not cause any new failures. Co-authored-by: Kiro <kiro-agent@users.noreply.github.com>
tautschnig
requested review from
kroening,
martin-cs and
peterschrammel
as code owners
November 13, 2026 09:00
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #9470 +/- ##
========================================
Coverage 81.02% 81.03%
========================================
Files 1723 1723
Lines 191326 191327 +1
Branches 73 73
========================================
+ Hits 155029 155039 +10
+ Misses 36297 36288 -9 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This branch has not been deployed
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
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.
An ASSUME false has no successors in the control-flow graph, so no instruction is control dependent on it. The full slicer therefore removed it unless it was the slicing criterion, which made the instructions that follow it reachable on paths that it blocked, resulting in spurious counterexamples. For example, each failing Java assertion is encoded as ASSERT false followed by ASSUME false, so that with --full-slice any later assertion was reported as failing with the values that violate the first one. Loops unwound by goto-instrument --unwind (without unwinding assertions) and function bodies generated with
--generate-function-body-options assume-false end paths the same way; in the latter case the slicer removed the call of the function.
Always retain ASSUME false instructions. Their control dependencies, and the calls of the function that contains them, are then retained as well. On jbmc/regression/jbmc-strings with --full-slice this fixes 6 tests and does not cause any new failures.