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
Fixed wasix network structure write in concordence to the read function #4166
base: main
Are you sure you want to change the base?
Conversation
Need to run regression on this change as while its quite trivial it may not be backwards compatible with some of the compiled WASM. Lets test it with...
|
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.
Ideally we'd have a C and a Rust snapshot tests for this.
One way to do it would be a simple tcp echo server.
But that will require a bit of time to write, I know.... not sure how urgent this is.
There is a workaround in wasix-libc, so lowering the priority |
…on (and to wasix-libc)
Co-authored-by: Syrus Akbary <me@syrusakbary.com>
54936dc
to
7c7fb87
Compare
It seems we want to move this forward, but we need to test a bit more |
Fixed wasix network structure write in concordence to the read function, and to wasix-libc.
Port is read as a "network endian" u16 but was wrote as a "big endian" u16, in practice reversing low/high byte of the u16.