Those warnings can be ignored, assuming you do not need to call typeinfo(std::exception), glMapBuffer or glUnmapBuffer.
The runtime abort is not a known limitation, that is something we need to figure out and solve. Any chance you can create a standalone testcase using that Swap function that I can debug? (I tried using it to swap some ints and that was fine, so it must be something more complex.) - Alon On Thu, Jan 30, 2014 at 8:47 AM, asnapper <[email protected]>wrote: > On Thursday, January 30, 2014 11:59:08 AM UTC+1, asnapper wrote: >> >> I cannot relate to what in my codebase triggers this error, so i'm >> wondering if I am hitting a known limitation of the new backend or if this >> is something you may want to look into? >> > > Just a little follow-up, I did some good old "printf debugging", and found > the code it fails on in my codebase. For some reason fastcomp chokes on our > sort algorithm: > > template <typename T> > inline void Swap(T& a, T& b) > { > T temp = a; > a = b; > b = temp; // here it fails > } > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
