yowl

> if they're both based on LLVMSharp (and not the RyuJIT IR plan). Why does using LLVMSharp preclude RyuJIT IR?

64GB, when I run it the memory graph in Task Manager shows just a small spike( not a great indicator, but something): 

I don't have anything with more than 64GB, unfortunately.

With emscripten it barely moves  I can try clang tip-of-tree with wasi-sdk, or when do you think v21 will be out?

If llvm 16 accepted a bug fix (assuming that's what it is), would wasi-sdk take it?

Thanks, it looks like upstream is fine. There is clearly a difference between `clang++` from the one from Wasi-SDK and https://github.com/llvm/llvm-project/releases/download/llvmorg-16.0.0/LLVM-16.0.0-win64.exe. Here is the output from Wasi-SDK's `clang++` and LLVM's...

I could try `-S` on a simple C program, I can't do it on this input as the SDK clang++ fails with `LLVM ERROR: out of memory`

Only thing I've noticed that is different is for WASI SDK the default target is different: ``` clang -cc1 version 16.0.0 based upon LLVM 16.0.0 default target wasm32-wasi ``` And...

Small update, `clang++` from the wasi-sdk for Linux is also fine: ``` scott@Matumbo:~/clang-repro$ ../wasi-sdk-20.0/bin/clang++ consoleclrjit.bc -o consoleclrjit.o -fvisibility=default -mllvm -combiner-global-alias-analysis=false -mllvm -disable-lsr --sysroot="e:\github\wasi-sdk/share/wasi-sysroot" -pthread -target wasm32-wasi-threads -c -g3 warning: overriding...

Tried with sdk 21 and problem persists: ``` C:\tmp>%WASI_SDK_PATH%\bin\clang++.exe -fvisibility=default -mllvm -combiner-global-alias-analysis=false -mllvm -disable-lsr --sysroot=c:\GitHub\wasi-sdk21\share\wasi-sysroot -c -g3 consoleclrjit.bc -o consoleclrjit.o -pthread --sysroot=%WASI_SDK_PATH%/share/wasi-sysroot -target wasm32-wasi-threads warning: overriding the module target triple...