This repository was archived by the owner on Apr 18, 2025. It is now read-only.
Bug: fix for JUMPI successful run case with zero condition and overflow destination
#382
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
…low-dest-for-zero-cond
lispc
deleted the
bug/jumpi-successful-run-with-overflow-dest-for-zero-cond
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Fix
testoolcasejumpi_d19(not-jump-hyperspace)_g0_v0.Reference go-ethereum opJumpi function, the
destinationis not checked with Uint64 overflow ifconditionis zero.TODO: may need to update with refactor PR #380.
Type of change
How Has This Been Tested?
Could test with
testoolcasejumpi_d19(not-jump-hyperspace)_g0_v0.And add a new unit-test case
jumpi_gadget_with_zero_cond_and_overflow_dest.