These functions were removed since we managed to remove all our allocations that occurred before startup.
This is/was an important thing for us to do as it allows wasm-ld (the static linker) to fully determine memory layout and specifically heap location without the need for post-link modifications to the wasm binary. You should be able simply call `_malloc` instead, or move your allocation in a C/C++ global? These are the two approaches that we used to remove all or our internal usage of dynamicAlloc. cheers, sam On Sun, Sep 13, 2020 at 8:04 PM Александр Гурьянов <[email protected]> wrote: > Hi. Just updated emscripten to 2.0.3, everything builds fine but now I > have error on module instantiation: > > ReferenceError: getMemory is not defined > > I checked the generated code of Module, and it have: > > Module["getMemory"] = getMemory; > > but getMemory itself never defined, for example in previous version it was: > > function getMemory(size) { > if (!runtimeInitialized) return dynamicAlloc(size); > return _malloc(size) > } > Also dynamicAlloc is not there. > > There are some new compiler flags? > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/CAKOm%3DVG-dBKPFWGowBuV7Ah%3DA1TLR1koBPBmJhNAY3cd4TcM0Q%40mail.gmail.com > . > -- 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/CAL_va2-1kXWHTVq4XCSzpJMvFhjEae45j3sG7JvM%2BBbUCQtUBA%40mail.gmail.com.
