Raptor Computing Systems Community Forums (BETA)
Software => Applications and Porting => Topic started by: pocock on June 16, 2021, 11:04:02 am
-
Does anybody know about support for Firefox WebAssembly (WASM) on ppc64le?
Some web sites like Zoom don't work without it.
Since March, it looks like Jitsi Meet may require WebAssembly too (https://community.jitsi.org/t/debian-firefox-78-esr-not-working-blank-window/101004)
Is WASM available in any recent version of Firefox? Can it be enabled if I rebuild Firefox from source?
-
There is no Wasm support currently. It's being worked on and we'd love contributors (right now it's primarily me with some help from chmeee): https://github.com/chmeeedalf/gecko-dev/commits/master
-
What's the status on this these days?
I found an open Mozilla issue for WASM (https://bugzilla.mozilla.org/show_bug.cgi?id=1860412). Is that just for the WASM portion (and there's other bugs tracking other portions), or is that tracking the entire JIT+WASM effort?
It looks like kth includes your patch for Firefox-esr v128 (https://github.com/chmeeedalf/gecko-dev/issues/5#issue-2459343753) in his archlinux package (https://github.com/kth5/archpower/blob/master/firefox-esr/PKGBUILD). And running that build of firefox in an archpower chroot scores quite a bit higher than fedora's firefox v133 on BrowserBench (https://browserbench.org/) (but also higher than the Firefox v130 from Archpower; it's not clear to me if the JIT patches are included there (https://github.com/kth5/archpower/blob/master/firefox/PKGBUILD)..)
-
It was working for awhile in internal test builds but changes to Firefox have caused it to crash on Wasm startup, deep within the code. I'm continuing to struggle with this and I'm trying to work on a better debugging setup as time permits.
A similar thing happens with Ion (second-stage) compilation, so they are probably related. Right now the JIT works but is limited to Baseline (first-stage) JS compilation and irregexp.
I haven't updated the patches for anything later than 128ESR yet but it's possible it may apply directly to more recent versions.
-
Well that explains why certain interactive pages have been erroring "WebAssembly not defined" when checking the developer console.
I just chalked it up to my user.js template disabling WASM.
-
Right now the JIT works but is limited to Baseline (first-stage) JS compilation and irregexp.
I haven't updated the patches for anything later than 128ESR yet but it's possible it may apply directly to more recent versions.
Ah, sweet! With the patches I can go into about:config (http://about:config) and enable wasm and baseline_jit and now my password manager works! That's honestly a big quality of life increase, lol.
-
Well that explains why certain interactive pages have been erroring "WebAssembly not defined" when checking the developer console.
I just chalked it up to my user.js template disabling WASM.
Although it may be possible to use some sort of Wasm interpreter or polyfill, obviously the best solution is to get the actual JIT working, of course. Otherwise, yes, there is no Wasm if there is no JIT.