Repository navigation
evm: Push 64-bit values to the stack without a temporary - #1799
Merged
Merged
Conversation
Contributor
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1799 +/- ##
=======================================
Coverage 98.24% 98.24%
=======================================
Files 186 186
Lines 17175 17176 +1
Branches 3921 3921
=======================================
+ Hits 16873 16874 +1
Misses 233 233
Partials 69 69
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
chfast
force-pushed
the
evm/push-uint64
branch
from
November 1, 2026 20:10
b44e229 to
9c91295
Compare
GCC 15 and 16 compile stack.push() of an integer by building the uint256 temporary in a stack slot and copying it to the EVM stack: 3 stores, 2 loads and 2 more stores instead of the 4 stores GCC 14 and Clang emit. This slows down PC, GAS, CALLDATASIZE, RETURNDATASIZE, MSIZE and the other instructions pushing an integer: CodSpeed measures them up to 20% slower with GCC 15 than with GCC 14. Add a push() overload for uint64_t which assigns the value to the stack slot, so GCC 15 and 16 compile these instructions as GCC 14 does. The two pushes of int64_t values, GAS and PC in Advanced, now cast explicitly instead of relying on the conversion to uint256.
chfast
force-pushed
the
evm/push-uint64
branch
from
November 1, 2026 20:13
9c91295 to
7693d83
Compare
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.
GCC 15 and 16 compile stack.push() of an integer by building the uint256 temporary in a stack slot and copying it to the EVM stack: 3 stores, 2 loads and 2 more stores instead of the 4 stores GCC 14 and Clang emit. This slows down PC, GAS, CALLDATASIZE, RETURNDATASIZE, MSIZE and the other instructions pushing an integer: CodSpeed measures them up to 20% slower with GCC 15 than with GCC 14.
Add a push() overload for uint64_t which assigns the value to the stack slot, so GCC 15 and 16 compile these instructions as GCC 14 does. The two pushes of int64_t values, GAS and PC in Advanced, now cast explicitly instead of relying on the conversion to uint256.