Sam Clegg
Sam Clegg
How much memory does the emscripten version clang use? I guess you could try building wasi-sdk with clang tip-of-tree to see if there is perhaps a bugfix?
wasi-sdk doesn't use tip-of-tree llvm, so the next major llvm update would be when llvm 17 is released (which could be a while).
Are you configuring emscripten to use your system version of clang? What version of clang are you trying to use and what version of emscripten? In general emscripten is only...
I see, you are matching our upstream revisions of llvm and binaryen precisely.... so its a mystery to me why it would work with upstream binaries but not with yours.
Figuring out which binary is hanging and why is the next step. Getting the output of `-v` will be useful.
So is that final command not returning? Can you see from `ps` or `top` what is actually still running?
Can you see what process is still running somehow? (There must be way to do that on windows). You can also try adding `EMCC_DEBUG=1` to the linker environment which will...
Are `C:\msys64\ucrt64/bin/wasm-emscripten-finalize` and `C:/msys64/ucrt64/opt/emscripten-llvm/bin/llvm-objcopy.exe` somehow a different type of process to `/ucrt64/bin/cmake` and `/usr/bin/bash`? Do you know why `wasm-emscripten-finalize` doesn't have a `.exe` on the end but `llvm-objcopy.exe` does?
So it seems that the `wasm-emscripten-finalize` binary that was built for msys2 is somehow hanging even though the official binary does not hang? Can you confirm this by simply replacing...
That makes sense. `wasm-opt` and `wasm-emscripten-finalize` are both built binaryen. It seems there is something wrong with binaryen binaries that are being used here. Can you double check that `wasm-opt...