Soni L.
Soni L.
yeah, it'd be helpful if that were somewhere in the emscripten docs (maybe alongside standalone wasm?). we did eventually figure out to look at llvm docs for it but it...
for context: memory.init (already) needs to know the data segment length so it can trap, but trapping isn't particularly useful for programs. a data.length would expose the length in an...
does this rely on stop_on_first_error=false?
at first glance, this looks like a GCC bug.
does this exhibit the problem? ```c /* min.c */ typedef uint32_t u32; typedef float f32; u32 w2c_float__exprs__88__wasm_f320x2Eno_trichotomy_lt_0(void* instance, f32 var_p0, f32 var_p1) { u32 var_i0, var_i1; f32 var_f0, var_f1, var_f2;...
we assume you did check the exit status? it doesn't output anything other than the exit status, but that might have been unclear, sorry.
indeed, it's supposed to return 0.
it can be minimized further, but you can probably do that a lot easier now.
btw, does `return (var_p0 < var_p1) | (var_p0 >= var_p1);` exhibit the problem?
*GCC, that's not how floats work* 🤦🏻♀️ thanks for confirming!