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

Memory load/store: bytes that are out of bounds should be written/read as 0 #222

Closed
wants to merge 3 commits into from

Conversation

jwasinger
Copy link
Contributor

@jwasinger jwasinger commented May 21, 2018

WIP

Fixes the test case randomStatetest283.

Fixes #221

@axic
Copy link
Member

axic commented May 21, 2018

I think we tried to break away from that EVM nonsense in ewasm :)

@jwasinger
Copy link
Contributor Author

Okay. I agree that trapping under these circumstances is better behavior.

@axic
Copy link
Member

axic commented May 25, 2018

I think practically this can be implemented in evm2wasm with returndatasize + zero-filling the different between the expected length of the call return area.

What other cases are there requiring this in evm2wasm?

@jwasinger
Copy link
Contributor Author

@axic Okay, closing this PR and we can continue tracking this in: ewasm/evm2wasm#250

@jwasinger jwasinger closed this May 25, 2018
@jwasinger jwasinger deleted the zero-fill-oob-mem branch May 25, 2018 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants