Soni L.

Unfortunately POSIX is a pre-security standard, so if your goal is compatibility with it then you need security to be opt-in. Alternatively you should ditch POSIX entirely. The thing about...

Okay, but that's a mechanism that wouldn't be usable by existing software (apps or even OSes), while a setsockopt extension would be. That's the tradeoff.

Okay so let's say a security-hardened OS wants built-in support for something like this. With socket options, it's just a matter of adding it. Replacing how sockets are opened is...

The thing is wabt currently uses "big-endian memory" to improve performance on some older platforms. Instead of storing memory as, say, ``` 04 03 02 01 00 00 00 00...

The current `wasm-c-api` is designed with LE hosts in mind. What could be done is to specify the behaviour on BE hosts. Specifically, one of: 1. Accessing linear memory, particularly...

nah we use `p[memsize-offset-readsize]` (e.g. `p[memsize-offset-1]` for bytes, `p[memsize-offset-4]` for u32, etc) and let the compiler figure out how to optimize it. not "true" negative indexing, just simple pointer math....

can we have a standardized `WASM_FLIP_MEMORY` for wasm-c-api?

defined like so: on big endian platforms, when compiled with `WASM_FLIP_MEMORY`, the host (wasm-c-api consumer) must access memory with an offset based on `memsize`, specifically `memory[memsize-wasmptr-readsize]`, where `memory` is the...

we want the engine to require a specific compile-time configuration, but an engine isn't required to support both modes. in fact most engines should only support one mode. wasm-c-api consumers...

No, the original title is correct. I want entry points/console scripts that use -m behaviour.