-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize interpreter::blockchain::{load_contract_code, code_copy}
to read contract starting from offset
#847
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
ab0cc7b
Copy directly into stack when loading contract code
acerone85 816390f
Update gas costs
acerone85 994008e
Merge branch 'master' into 681_remove_storage_read
acerone85 ded2cff
Update changelog
acerone85 ccfbb61
Merge branch 'master' into 681_remove_storage_read
acerone85 ef32062
Revert optimization on LDC
acerone85 0280827
Merge branch 'master' into 681_remove_storage_read
acerone85 83a97ba
Merge branch 'master' into 681_remove_storage_read
acerone85 8c6ced6
Remove TODO comment
acerone85 bd00e21
Isolate load contract code to helper function
acerone85 010dd6f
Address clippy's errors
acerone85 d67dd77
WIP: Change Storage Read trait
acerone85 470cd31
Merge branch 'master' into 681_remove_storage_read
acerone85 226330a
Reset to master
acerone85 c6ae75e
Optimize load_contract and code_copy to read contract starting from s…
acerone85 5cfd978
Changelog
acerone85 b64929f
Merge branch 'refs/heads/master' into 681_remove_storage_read
xgreenx 4e228be
Apply suggestion from the review.
xgreenx ba2d17a
Return right error in the case of non existing source
xgreenx 26e6cd7
Merge branch 'master' into 681_remove_storage_read
xgreenx File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We never read more than
length
bytes with the new version. Shouldcharge_len
be changed accordingly to reflect this?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be a breaking change, and should be done separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also prefer to keep the current charging strategy, even if we overcharge user=) The
length
in most cases should be not more thancontract_len
.