> On May 12, 2025, at 06:24, Damien Stewart <[email protected]> wrote:
>
> On 12/5/25 1:49 am, John Paul Adrian Glaubitz wrote:
>> Since you’re already working on this issue, please take the time to file an
>> upstream bug report.
> I just need to find the right place to file it. Did some research on WASM
> today and found it is designed for LE only. I've also found some bug reports
> that bring up issues related to BE and it always comes back to not supported
> and road blocked. So if I don't want to file YABEI (yet another big endian
> issue) that gets an immediate won't fix. I just need to find the right place
> place and/or way to describe it to be accepted.
>>
>> And if you come up with a patch, please forward it upstream. I don’t have
>> the time and nerves to work on this issue.
> I could see why. At this point in the game, making use of compiler attributes
> like GCC to mark scalar byte order are looking good, even if it would look
> like a hack. But, since code these days relies on CPU specific byte order and
> clean portable code is a relic of the past, such compiler dependent features
> are looking good to me.
>
>
wasm will only ever be little endian by design.
I think the issue lies in RLBox, which needs to account for BE systems when
using wasm, but does not.
Ken
> --
> My regards,
>
> Damien Stewart.
>
