Both wasm2c and wasmtime are known for supporting storing v128 lanes in reverse order on big-endian platforms. It would be nice if simde supported it too, as it would simplify wasm2c a lot without adding too much complexity in simde. Since a v128 acts as a slice of wasm memory, it should be aware of how wasm memory is represented on the host. You may want to take a look at webassembly/wabt#2340 for more details.
(We do note that forcing this big-endian representation on little-endian hosts has its uses, even as it goes against the wasm spec. In particular it makes running some regression tests (e.g. in pull requests) much faster than running the full test suite in qemu.)
Both wasm2c and wasmtime are known for supporting storing v128 lanes in reverse order on big-endian platforms. It would be nice if simde supported it too, as it would simplify wasm2c a lot without adding too much complexity in simde. Since a v128 acts as a slice of wasm memory, it should be aware of how wasm memory is represented on the host. You may want to take a look at webassembly/wabt#2340 for more details.
(We do note that forcing this big-endian representation on little-endian hosts has its uses, even as it goes against the wasm spec. In particular it makes running some regression tests (e.g. in pull requests) much faster than running the full test suite in qemu.)