Ah so it's a Binaryen thing, not clang's WASM backend. Good to know :)
Thanks!
On Saturday, 20 June 2020 23:04:02 UTC+2, Thomas Lively wrote:
>
> WebAssembly itself doesn't have any compression in its data segments, but
> Binaryen does split up data segments around ranges of zeroes as an
>
WebAssembly itself doesn't have any compression in its data segments, but
Binaryen does split up data segments around ranges of zeroes as an
optimization. That transformation depends on the memory being initialized
to zero when it is created, making zeroes in data sections redundant.
On Sat, Jun
I just noticed something interesting... through a stupid mistake on my part
I accidentally added 4 MBytes of bloat to my native-compiled executables,
because I statically initialized some innocent looking members of a very
big global struct variable (so that this global struct only had a
> What's your experience with mobile webapps and keyboard support?
It massively *sucks* :D
I explored a "solution" which involves a hidden HTML text field, focusing
that text field to bring up the keyboard, and unfocusing it to hide the
keyboard again. It kinda works, but it has all sorts of
Hi,
Mobile browsers are making progress with WebAssembly support and I see
more interest in handling on-screen keyboards in web games.
(typically so your game's port doesn't get the mobile player stuck with
a mere "whose your name" prompt).
I explored 2 main ideas to make the virtual keyboard
I agree with Alon, even though it's not "good practice" to have
include/emscripten in the search path, the problems that result from such a
name collision might be too confusing because nothing points to the file
include/emscripten/math.h being the problem (also the function in
