Thanks for reporting, this is a bug. The stack* methods are implemented in emscripten.py, not support.js, which is how they got missed when implementing the new export functionality.
Fix is in https://github.com/kripken/emscripten/pull/6345 - Alon On Sun, Mar 18, 2018 at 11:00 AM, Thorsten Möller <[email protected]> wrote: > Hi > > While trying move from ASM to WASM, it seems that the functions > `stackSave` and `stackRestore` are no longer available when compiling with > `-s WASM=1`. Using latest version 1.37.36 and even if we add > `EXTRA_EXPORTED_RUNTIME_METHODS=['ALLOC_STACK','allocate','stackSave','stackRestore']` > these two functions are no longer defined in `Module` (the former two in > the array are). We have used these functions so far in a small wrapper of > one of our library (written in C) to allocate and release memory on > Emscripten's stack, e.g.: > > var stack = Module.stackSave(); > var pName = Module.allocate(Module.intArrayFromString(name), 'i8', Module > .ALLOC_STACK); > // ... invoke some library function > // finally restore stack position > Module.stackRestore(stack); > > How should this be done when compiling for WASM? > > Thanks > > -- > 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]. > 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]. For more options, visit https://groups.google.com/d/optout.
