Clarification for some settings: are they for Asm.js or Wasm ?

Another technical question for today: There is a couple of Emscripten settings for which it is not clear if they have an impact/use on Wasm backend: - DOUBLE_MODE - PRECISE_F32 I suppose both of them are only useful for Asm.js, but this is not 100% clear to me. So I just wanted to know :)

Defining TOTAL_MEMORY and PTHREAD_POOL_SIZE at wasm instantiation time

Hello, I have some question related to TOTAL_MEMORY and PTHREAD_POOL_SIZE: Is it possible to define (or override) these value at Wasm instantiation time, instead of at compilation/link time. The reason for TOTAL_MEMORY is the following: when compiling with threading support (USE_PTHREADS=1)

Re: How to Catch Code Corruption

Hmm, those look like all the relevant flags already. The one thing I'd worry about is if they don't all work together properly for some reason. I'd try for example just running with the sanitizers, but none of the emscripten-specific ones (SAFE_HEAP, STACK_OVERFLOW_CHECK). Also note that you need

How to Catch Code Corruption

I have a pretty hefty program (~12Mb) which works well for the most part. It uses WebGL and an HTML5 Canvas object. I can throw source from numerous files at it and it behave ok. The problem is when I start resizing the Canvas I encounter corruption of the code. A function that has been called

Re: How to Catch Code Corruption

Alon, Thanks for the info. I will try those suggestions. On Tuesday, December 3, 2019 at 10:04:41 AM UTC-6, Mark Meier wrote: > > I have a pretty hefty program (~12Mb) which works well for the most part. > It uses WebGL and an HTML5 Canvas object. I can throw source from numerous > files at

Re: Clarification for some settings: are they for Asm.js or Wasm ?

Maybe the options should also be grouped, so that all the fast-comp options will be next to each other, and the same with the LLVM options? It will make the document significantly easier to go over. On Tue, 3 Dec 2019 at 19:45, Alon Zakai wrote: > Good idea! I opened > >

Re: Clarification for some settings: are they for Asm.js or Wasm ?

Good idea! I opened https://github.com/emscripten-core/emscripten/pull/9949 All the ones you mentioned here are fastcomp-only, except for INLINING_LIMIT which definitely should affect closure's inlining, and should also affect LLVM (but we should probably check that, as I'm not sure). On Tue,

[Discord] Join us to discuss WebAssembly

[image: WebAssembly.jpg] I just create a discord server named “WebAssembly” to discuss sth about it. So if you are interested to do some research or exchange some experience about best practice, JUST JOIN US ! Discord: https://discord.gg/AE89YTx -- You