I noticed that the Javascript "binary" that is generated by the latest emscripten from incoming (combined with the corresponding emscripten-fastcomp, emscripten-fastcomp-clang versions) is a lot larger than what it used to be a while ago (I did not update my local emscripten fork for 2 months or so). From the looks of it this is due to the fact that what used to be multiple allocate(...) calls is now one massive allocate(...) call with recurrent intermittent sequences of 0.
I basically updated my emscripten fork to benefit from the new ALLOW_MEMORY_GROWTH flag. Does the latter have anything to do with the single allocate(...) call? 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]. For more options, visit https://groups.google.com/d/optout.
