-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Create EIP for frame-pointer-relative memory addressing #3337
Conversation
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.
Only the frontmatter change is required to merge as draft.
EIPS/eip-3337.md
Outdated
type: Standards Track | ||
category: Core | ||
created: 2021-03-06 | ||
requires: <EIP number(s)> |
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.
requires: <EIP number(s)> |
Co-authored-by: Micah Zoltu <micah@zoltu.net>
Co-authored-by: Micah Zoltu <micah@zoltu.net>
Co-authored-by: Micah Zoltu <micah@zoltu.net>
@MicahZoltu PTAL |
For blocks where `block.number >= FORK_BLOCK`, the following changes apply. | ||
|
||
### Frame pointer | ||
A new EVM internal state variable called the "frame pointer" is introduced. This is a signed integer that starts at 0. |
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.
Probably needs to be specified as 256-bit twos-complement for the sake of the GETFP and SETFP operations.
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.
You may want to bring this up in the discussions-to to make sure it gets seen. I agree that this needs more specificity!
Side note: We probably don't need 256-bits, likely 32-bits would be way more than enough?
Introduces four new opcodes for loading data from and storing data to memory offset by a frame pointer.
No description provided.