dev: bumped addresses in range of 0x100 #1372
Merged
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
enitrat
force-pushed
the
refactor/bumped-addresses-0x100
branch
4 times, most recently
from
8832e23
to
ee5064e
Compare
enitrat
force-pushed
the
refactor/bumped-addresses-0x100
branch
from
ee5064e
to
2da2300
Compare
enitrat
force-pushed
the
refactor/bumped-addresses-0x100
branch
from
123a6d5
to
946e4fa
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 PR modifies test fillers that caused conflicts when using address in range 0x100 along with RIP-7212 precompiles.
The addresses have been bumped from 0x100 to 0x1000, and the test logic updated accordingly.
The test fixtures have been re-generated using retesteth.
Fixes #1371