We do that too, but ASLR and the continued prevalence of 32-bit browsers (on 64-bit OS no less) signficantly cuts into the available contiguous memory to Emscripten. I hope at some point, Emscripten makes the jump to 64-bit addressable memory. Even then, having no way to increase heap size (to start small and grow) will be a big limiter to the technology. I can't see allocating 2^54 bytes at startup. Thanks for the suggestions.
On Thursday, September 11, 2014 4:16:02 PM UTC-7, Nicholas Wilson wrote: > > Good points, fair enough. We just increase the heap size at link-time in > our builds, but I can certainly see that emscripten's memory management is > going to cause trouble in real scenarios. It seems pretty brave to ship > stuff on a platform where you have to have a malloc() wrapper like that! > > Nick > > On Friday, 12 September 2014 00:01:53 UTC+1, Alecazam wrote: >> >> I don't think I'd mentioned 4-byte alignment. I typically align to 16 >> bytes (as per the defines). That way SIMD can be mixed in with non-simd >> structs without needed custom allocator everywhere. >> >> Abort on failure is an issue since Emscripten has a fixed size heap. >> > -- 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.
