If you pass -mbulk-memory to emcc while using the LLVM backend, it will automatically lower memcpy, memmove, and memset to use their bulk memory instruction equivalents. That should work today.
The plan is to land conditional segment initialization using memory.init and data.drop instructions in the linker once bulk memory operations ship by default in stable chrome. That will allow emscripten to use threads without separate memory init files. On Wed, May 15, 2019 at 9:56 PM Soeren Balko <[email protected]> wrote: > Just saw that Chrome has WebAssembly bulk memory operations in beta. Are > there any short-term plans to make these available behind a flag in > Emscripten? > > Thanks, > Soeren > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/f2f90663-974d-497c-9bbc-b29026483a49%40googlegroups.com > <https://groups.google.com/d/msgid/emscripten-discuss/f2f90663-974d-497c-9bbc-b29026483a49%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAJZD_EU1uHR4G85MjusFVimYt98PikZ%2BaZs_UnDAx1yh2GYp_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
