Repository navigation
Conversation
| val startcontext: unit -> C.t | ||
|
|
||
| (** @raise Deadcode if resulting state is unreachable. *) | ||
| val sync : (D.t, G.t, C.t, V.t) man -> [`Normal | `Join | `JoinCall of CilType.Fundec.t | `Return] -> D.t |
Member
There was a problem hiding this comment.
What does it mean for sync to raise Deadcode?
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.
In the light of #2206 and possibly others, this PR documents the
Deadcodeexception and which transfer functions may raise it, and crucially which shouldn't.The latter currently are
query,enterandthreadenter. This is based on whichMCPtransfer functions handleDeadcodecorrectly (usingmap_deadcode), while these three don't.For some of the rest, e.g.,
body,skipandreturn, it may be questionable if they ever should, but at least it's supported by the framework.TODO
raise Deadcodeduringquery? That might break something and reveal existing issues.