-
Notifications
You must be signed in to change notification settings - Fork 284
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
Unexpected behavior with load/store alignment #570
Comments
Hmmm as with the other issue running Wasmtime results in the same output without your expected exception. Can you elaborate what you used to verify that your expected output is as specified by the Wasm standard? |
Thank you four your reply. |
Okay thanks for letting me know about all these other runtimes. Can you verify though that Wasmtime also has this same behavior as |
On my computer, the wasmtime can output the same thing. as |
I was reading about memory load and store operation alignment semantics in Wasm and found this explanation: https://rsms.me/wasm-intro#addressing-memory So according to this source it seems to me that |
@erxiaozhou it would be nice to know if you agree with my interpretation or disagree so we can either close this or find an agreement. |
Thank you for your nice reply. I'm reading the explanation link, and I'll decide my opinion in a few hours. So I wish you could wait for me for hours, thank you! |
reply_wasmi_570.zip
There is no error when I execute I am looking forward to your reply, thank you! |
Hmmm, if this is true then it might imply a bug in the For |
Thank you for your insights and patient reply! I have tried different values for the byte which represents |
Interestingly trying to turn the Wasm file into a
In this case 64 refers to the given |
@erxiaozhou I just tried your provided @erxiaozhou Can you confirm this so that we can close this issue? I tested with version
And also the current |
Strongly connected to this Wasmtime issue: bytecodealliance/wasmtime#5344 |
The linked Wasmtime issue was just triaged and found to be fixed. (bytecodealliance/wasmtime#5344 (comment)) Thus, once we update to the new |
Description
Current State
Output: 65508521924046110000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Expected
An exception indicating that "alignment must not be larger than natural"
Environment
Steps to Reproduce
wasmi.zip
wasmi <test_case_name> to_test
The text was updated successfully, but these errors were encountered: