Zoltan Varga
Zoltan Varga
Currently, our .net for WebAssembly project is built on top of LLVM, i.e. we compile .net bytecode to LLVM bitcode to wasm.
/azp run runtime-wasm
/azp run runtime-wasm
This approach is not going to work, for example: ``` public class Tests { private interface INegator where T : struct { static abstract bool NegateIfNeeded(bool equals); } private readonly...
Closing in favor of: https://github.com/dotnet/runtime/pull/76033
Maybe put the usage inside an #ifdef CORECLR for now and disable the relevant tests for mono ?
So this error is reported by the runtime when the app tries to load an assembly which doesn't match the assembly the aot code was generated from. Its either a...
The calling convention used by the runtime was changed in 7.0 to conform to the wasm calling convention spec: https://github.com/WebAssembly/tool-conventions/blob/main/BasicCABI.md According to the spec, small structs which fit in one...
Same issue as: https://github.com/dotnet/runtime/issues/78889
> @vargaz How come it only happens in the app store? shouldn't Release builds deployed on device produce the same problem? No idea, but the underlying problem appears the same.