Skip to content
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

fix(levm): add function to assign bytecode to callframe #1483

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

JereSalo
Copy link
Contributor

Motivation

Description

  • When changing the bytecode of current callframe we also have to calculate valid jump destinations of that bytecode. There is only one case in which we are doing this right now. In a Create type Transaction at the end of the validations the calldata is assigned to the bytecode.

Closes #issue_number

@JereSalo JereSalo added the levm Lambda EVM implementation label Dec 12, 2024
@JereSalo JereSalo self-assigned this Dec 12, 2024
@JereSalo JereSalo marked this pull request as ready for review December 12, 2024 12:58
@JereSalo JereSalo requested a review from a team as a code owner December 12, 2024 12:58
@ilitteri ilitteri enabled auto-merge December 12, 2024 13:00
@ilitteri ilitteri added this pull request to the merge queue Dec 12, 2024
Merged via the queue into main with commit cd265cc Dec 12, 2024
5 checks passed
@ilitteri ilitteri deleted the levm/assign_bytecode branch December 12, 2024 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
levm Lambda EVM implementation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants