Hi Damien, Thanks for providing these insights!
On 2025-07-10, Damien Stewart <[email protected]> wrote: > This is running deep. Of course, this is due to taking perfectly > portable code, compiling it into little endian machine code, then > reverse engineering that into an analogous C source. The result has > ended up with introducing a false dependence of little endian. Be good > if wasm2c could be told to generate big endian or portable code. But > since the world is now running on a little endian web, this problem > won't go away now. It seems to me that this is where the big-endian/browser community should be focussing its efforts: wasm2c generating portable code. John Ogness
