> > > > It may well be that lli doesn't work with emscripten's bitcode any longer > after the change to the current target triple. > > > Well that would be really bad. How else would I be able to find the offending machine instruction that might be translated the wrong way by Emscripten in millions of statements?
Also I think its a C++ issue. I have now started to replace things like std::vector<> & stuff with my own ultra slim & simple implementations which basically all come down to a single "realloc". So far I have been able to successfully compile & run my above sample program without modification (except that I am no longer using libcxx, but my own C++ headers). I think for now I may go down the route of just replacing all C++ specifics with my own super-simple implementation so that LLI doesn't choke itself. But I fear that as soon as I start incorporating the huge game library, there will be stuff that breaks even with all my own headers. -- 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.
