hmm this would explain the different timings. but 2 seconds to zero out a larger bunch of memory?!? is the resulting javascriptcode really so slow? here are some timing on a native build on the same machine:
malloc/free: 0.0002104s vector ctor: 0.019273s vector resize: 0.0157814s vector reserve: 0.0001271s this is about 20 times faster than firefox and 100 times faster than IE for the vector ctor. Am Mittwoch, 18. Mai 2016 14:14:07 UTC+2 schrieb AlainC: > > For malloc and reserve (with an initially empty array), there is no > initialization of the elments in the array. > For std constructor and resize, each element will be initialized > individually (to 0) in a loop I think. > -- 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.
