Then, what about the *asm.js*-cases? Does *emscripten* give errors for unsupported feature rather than just producing incomplete output?
2018년 12월 1일 토요일 오전 5시 19분 8초 UTC+9, Sam Clegg 님의 말: > > On Fri, Nov 30, 2018 at 12:03 PM <[email protected] <javascript:>> wrote: > > > > Hi. > > > > Does LLVM backend compiler for WASM 100% ensure that there will be no > semantic differences or bug after compiling c++ to WASM? > > By semantic difference, I mean the different output due to incomplete > translation. > > > > There are certainly things that the LLVM backend doesn't yet support > (the one that comes to mind is computed-gotos). I those cases the > backend will error out rather than generate "incomplete" output. > > > Thanks. > > > > -- > > 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] <javascript:>. > > > For more options, visit https://groups.google.com/d/optout. > -- 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.
