- From: David Ross <sw1ayfe@gmail.com>
- Date: Fri, 03 Mar 2017 13:53:31 +0000
- To: public-webassembly@w3.org
- Message-ID: <1488549211.4503.7.camel@gmail.com>
WASM is being switched on from Firefox 52 (7 March, 2017). Chrome will follow the next version rollout, the next week possibly? I'm using Nightly (54) on Arch Linux on a 2008 model Dell laptop running 16Gb RAM and 1) now works fine. It did not a few months back when I last tested. 2) not sure of your precise test here to compare On Thu, 2017-03-02 at 09:25 -0700, Doug Royer wrote: > Just started playing with wasm. > > Tried several version of Firefox and Chrome. > > Running Linux, Fedora-24 > > (1) http://webassembly.org/demo/ > > Starts up a loading page, then after the load slider is > finished, products a BLANK page > > (2) The HelloWorld demo, generates: > > An Exception thrown, see JavaScript console, on the browsers. > > (2.1) the "emrun --no_browser --port 8080 ." > prints this when the browser access the page: > > The html page you are running is not emrun-capable. Stdout, > stderr and exit(returncode) capture will not work. Recompile > the application with the --emrun linker flag to enable this, or > pass --no_emrun_detect to emrun to hide this check. > > (2.2) Compiling with "--emrun", produces the same error as (2) > > (2.3) Compiling with "--no_emrun_detect", results in (at compile time) > > clang-3.9: error: unsupported option '--no_emrun_detect' > ERROR:root:compiler frontend failed to generate LLVM bitcode, > halting > > Questions: > > What browsers versions work? > > Are the http://webassembly.org/getting-started/developers-guide/ > incorrect? > > Thanks! >
Received on Monday, 6 March 2017 10:24:14 UTC