Thank you Alon! So if I understand correctly it should not happen in wasm? Interesting, because this would be exactly my case.
W dniu czwartek, 13 września 2018 19:32:26 UTC+2 użytkownik Alon Zakai napisał: > > It's usually fine to ignore that, unless your codebase cares about > differentiating NaNs (which is rare). > > The issue is that in asm.js we have just the single JS NaN, and can't emit > literals for any others. In wasm though this is not an issue. > > On Thu, Sep 13, 2018 at 4:23 AM Jendker <[email protected] <javascript:>> > wrote: > >> I checked it one more time here and I am really not sure, what causes it. >> Seems that it is somehow connected with compiled OpenCV library though. >> >> W dniu czwartek, 13 września 2018 13:06:01 UTC+2 użytkownik Jendker >> napisał: >>> >>> After starting using OpenCV algorithm I get the following warning during >>> linking: >>> emcc: warning: cannot represent a NaN literal '0x4f52cf0' with custom >>> bit pattern in NaN-canonicalizing JS engines (e.g. Firefox and Safari) >>> without erasing bits! >>> >>> I tracked down, that initialization of the algorithm object gives me >>> such warning. Is it something I should care about? >>> >> -- >> 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.
