[Webkit-unassigned] [Bug 181373] [GTK] webkitgtk-2.18.4 build error on 32-bit OS with WEBASSEMBLY=ON

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jan 12 14:05:41 PST 2018


https://bugs.webkit.org/show_bug.cgi?id=181373

--- Comment #11 from Konstantin Tokarev <annulen at yandex.ru> ---
(In reply to Vadim from comment #10)
> > > Are there plans to make webassembly work for 32-bit builds?
> 
> > Definitely not, sorry. It's unclear if even the baseline JIT will remain supported on 32-bit.
> 
> It's so cute how "portable" the "portable" web is :( It runs on everything
> if the everything is amd64... never mind.

I hope the latter won't happen in nearby future, but B3 is not going to support 32-bit platform either (and our WASM has hard dependency on B3 now; this has a bit more chance to bid changed in future but don't hold your breath)

Yes, WASM is marketed as a portable thing, but to be actually useful it has to run fast. This requires sophisticated JIT, close to native compilers, and these things are not easily portable. Try running asm.js stuff compiled from C++ without JIT, it will run "fine", but you probably would be more happy if it didn't.

> $ gcc -dumpmachine
> x86_64-unknown-linux-gnu

I see, we cannot get it into account then.

> Getting browsers eat less memory was one of the primary reasons to have
> 32-bit userspace for me.

I once was sharing this attitude, but in reality lack of general purpose registers and specifics of JS VM make 32-bit x86 an especially poor option.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180112/53c944cb/attachment.html>


More information about the webkit-unassigned mailing list