Dan Gohman

It's something we're interested in, but there is not yet a specific path. In theory, UBSan ought to be pretty straightforward, configuring the build and UBSan to be enabled for...

For the trap messages, Wasmtime recently changed its output to format the backtrace offsets differently. The change you have here is fine for now, though of course it'd be good...

Thanks for pointing that out -- `-DCMAKE_C_COMPILER_WORDS` is actually an old workaround for problems which have since been fixed properly. I submitted https://github.com/CraneStation/wasi-sdk/pull/20 to remove it.

As a quick update, it turns out removing the `-DCMAKE_C_COMPILER_WORDS` did break things, because I was getting files from previous builds when I was testing it. I'll try using `-DCMAKE_TRY_COMPILE_TARGET_TYPE=STATIC_LIBRARY`...

That appeared to have problems as well, that I didn't see in my local builds. See #20 for details.

Thanks for the report, this is indeed a bug! It appears that this is an instance of https://bugs.llvm.org/show_bug.cgi?id=28954 . Another workaround is to add `-lc++` to the command-line, before any...

@sbc100 Is there an update on the status of that patch?

Awesome, thanks!

@ldionne Do you know if https://reviews.llvm.org/D31413 was cherry-picked into LLVM 11? Either way, https://github.com/WebAssembly/wasi-sdk/pull/178 updates wasi-sdk to LLVM 12, which will hopefully resolve this.

I can reproduce this error with this testcase: ```c int foo(int (*p)(void)) { return p(); } ``` compiling with -save-temps with the latest wasi-sdk release. It appears fixed on LLVM...