change 'no-assume-stack-scope' to 'assume-stack-scope' #442
Conversation
This file contains 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
thebendavis
reviewed
Sep 4, 2024
…ntation This flips the default behavior of this unsafe flag. If set, 'assume-stack-scope' injects an additional assumption into every pre-domain that all out of scope stack values (i.e. past the stack pointer) This is a fairly strong assumption that is unsafe in general, in particular it will crash in the case where it is provably false (i.e. the value domain implies that the stack contents past the stack pointer are necessarily inequivalent) updates challenge10.args to use --assume-stack-scope
danmatichuk
force-pushed
the
dm/flip-stack-scope-asm
branch
from
10e80fd to
7ae9fa7
Compare
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.
This flips the default behavior of this unsafe flag.
If set, 'assume-stack-scope' injects an additional assumption into every pre-domain that all out of
scope stack values (i.e. past the stack pointer)
This is a fairly strong assumption that is unsafe in general, in particular it will crash in the case where it is provably false (i.e. the value domain implies that the stack contents past the stack pointer are necessarily inequivalent)