Luuk de Gram

> I disagree with using a compiler-rt function when there is a directly supported wasm operation. If the compiler-rt function is faster than the native operation, that is a problem...

Thank you for your patience, my break took a bit longer than originally anticipated. Great work, I'm confident in the solution that was implemented so will give this a merge.

This was changed in #14102. The language reference needs to be updated to reflect this change. The PR provides examples of how to export functions to the host environment. I've...

Thanks for reporting and clarifying this with me. I'll have a fix ready for both `undefined` and zero values this week :)

The main reason for the allocator is to prevent leaking as much memory. There's currently no `memory.shrink` instruction (yet). This means that each thread spawn would leak its memory upon...

@mlugg Fixed it for the Wasm backend :)

> ping @andrewrk @Luukdegram 🙏 I'm currently on holiday and won't be able to take a look at this for the next 2 weeks.

> hey @Luukdegram / @andrewrk any further changes you would like to see? Not necessarily from my side. I'll leave the final judgment to Andrew as he mentioned he had...

Those values are defined by the operating system. Why should those be defined when targeting `freestanding`?

> I believe they should be defined by `libc`. I'm a little uninformed about how libc is supposed to work with `wasm32-freestanding`. It appears that there are header files provided...