https://bugs.llvm.org/show_bug.cgi?id=35385
jgrave...@google.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
--- Comment #9 from jgrave...@google.com ---
My point is more that it doesn't really fix this bug at all. It just changes us
from failure to build a valid wasm object file, to failure to link
independently-valid-but-disagreeing wasm object files.
It also breaks EM_ASM in C
(https://logs.chromium.org/v/?s=chromium%2Fbb%2Fclient.wasm.llvm%2Flinux%2F26661%2F%2B%2Frecipes%2Fsteps%2FExecute_emscripten_testsuite__emwasm_%2F0%2Fstdout),
which long-term I don't really mind because it's using a pretty fragile
mechanism (i.e. prototypeless C function declarations, that are not even
well-defined because they are expected to have mismatching callsites).
Short-term it might be good to revert this until we can get EM_ASM not relying
on that behavior (which I have some ideas around solving once and for all).
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
