Sam Clegg

This does work with clang. Its ends up having the same effect as `--target=wasm32-wasi`. I actually think it more like a normal target if you can just do `CC=/path/to/wasi-clang make`...

I was imagining one could put `/opt/wasi-sdk/bin` at the end of your PATH then you can call system clang via `clang` (since it will see the system one, e.g. /usr/bin/clang,...

I think the way to fix this is to pass the `CMAKE_OSX_DEPLOYMENT_TARGET` to cmake. On the WebAssembly/waterfall build we use `-DCMAKE_OSX_DEPLOYMENT_TARGET=10.12`. We should probably do that same here.

For more info on the current status of thread support see https://github.com/WebAssembly/wasi-libc/issues/209. (In fact, this issue should probably be moved to wasi-libc). I think we probably should include a version...

;TLDR: I'm not sure Its not clear what the major wins would be, but I'm open to being convinced. Having just one parser would clearly be great, but have to...

> Just curious: > > > there are other things in do in wabt that would be more valuable to invest it > > What are they? Nothing specific, just...

Oh wow! Thats exciting. Would it not make sense to wait for wasi to stabilize though? Baking wasi_unstable into node seems a little early no?

I don't see any occurrences of `assert_return_canonical_nan` or `assert_return_arithmetic_nan` in this repo. wabt passes all the tests in the repo (which are mirrored in `https://github.com/WebAssembly/testsuite/tree/master/proposals/bulk-memory-operations`) Am I missing something?

Oh I see the problem. I'm only looking at the actual bulk memory tests because the testsuite repo only includes tests that have be modified from upstream: https://github.com/WebAssembly/testsuite/tree/master/proposals/bulk-memory-operations The solution...

Aren't you doing to have to lookup the memory refereed to by `memindx` anyway when doing a load or store? e.g to look up its bounds?