Sam Clegg

#23537 shipped in 4.0.3 and we haven't heard anything about this issue yet. I propose that we land this soon-ish since its already causing issue on my desktop machine to...

How about failing at link time with an error like `build with -s FAKE_SIGNALS if you want fake signal support`? or do you think we want the portable fake signals...

@kripken was looking into this I believe. As of right now I don't think there is any support for this on the LLVM side.

> The memory64 proposal has updated legacy test scripts like `table_file.wast` and added table64 tests rather than creating say `table64_fill.wast` which largely has been the convention with proposals in the...

wasm-decompile doesn't currently have a maintainer, or anyone who works on it. If you would like to send PR please do.

Do you use `dlclose` on this way on native platforms? if so then this could be a bug in our implementation of `dlclose`. `dlclose` is not something that our users...

I think the problem is maybe more like "symbols from subsequent dlopen() operations don't override existing global symbols from previous dlopen() calls". Does this work for you on native platforms?...

You say in the title "clang-repl can do the undo operation to surpass redefinitions and stuff.".. I assume you mean the native clang-repl? My question is does the native clang-repl...

I don't think you can currently expect dlclose followed by dlopen to replace symbols in the global namespace. I think the first dll to provide I symbol will currently win...

Sounds like a real bug. Its not too surprising to me that there might be bugs or differences in behaviour around dlclose since I don't imagine its used much in...