yowl
yowl
More info, the x86 version of clang++ fails as above, the x64 version passes. Is there a reason the SDK uses the 32 bit version, do LLVM even support that...
Wasi-SDK includes the 32 bit version.
Sure: ``` C:\github\runtimelab>dumpbin /headers %WASI_SDK_PATH%\bin\clang.exe Microsoft (R) COFF/PE Dumper Version 14.38.33135.0 Copyright (C) Microsoft Corporation. All rights reserved. Dump of file c:\github\wasi-sdk21\bin\clang.exe PE signature found File Type: EXECUTABLE IMAGE FILE...
Yes, I confirm that `clang` fixes the issue ``` C:\tmp>"C:\Users\scott\Downloads\wasi-sdk-21.0+m-mingw.tarx\wasi-sdk-21.0+m\bin\clang.exe" -fvisibility=default -mllvm -combiner-global-alias-analysis=false -mllvm -disable-lsr --sysroot=E:\GitHub\wasi-sdk\share\wasi-sysroot -c -g3 c:\tmp\consoleclrjit.bc -o c:\tmp\consoleclrjit.o -pthread --sysroot=%WASI_SDK_PATH%/share/wasi-sysroot -target wasm32-wasi-threads warning: overriding the module target...
Thanks will convert this to an issue.
I have a fix incoming, which at least solves the variant problem
> I have a fix incoming, which at least solves the variant problem https://github.com/bytecodealliance/wit-bindgen/pull/945
~~Are there any nuget packages for v15 ?~~ Ignore that, I was using feeds from https://pkgs.dev.azure.com/dnceng/public/ only
Can opaque pointers be used in LLVM sharp v15, I can't see how to get the type from the context/addr. space?
@robert-matusewicz Hi, did you have a chance to do anything for this, I had a look at Wasm binary operations and LLVM binary operations and there's nothing there that will...