Matthew Fluet

Should this issue remain open?

Yes, the native codegens store GC information in the text segment, in the memory immediately preceeding a return address. The C and LLVM codegens use a different mechanism, and so...

This looks very nice; I'm pleasantly surprised at how minimal the PR is to support WebAssembly/WASI.

@agoode is this PR ready to be merged? It seems that it is working well for the Twelf project.

Looks good. (Either I missed it or changing to "ready for review" didn't re-raise the issue in my notifications.) In `runtime/Makefile`, I will probably change the `WASMTIME` variable to something...

Short answer to naming tool executables: the `-llvm-as `, `-llvm-llc `, and `-llvm-opt ` compile-time arguments can be used to specify the names of tool executables. In order to avoid...

I don't know that I would really consider that to be a bug. There are other places where MLton will report an error message without the exact same text as...

Can you provide more details? The architecture and os where the failure is being observed? It looks like this is a self-compile that is failing. The "Unable to allocate 804,197,972...

You might try compiling using `make MLTON_RUNTIME_ARGS="gc-messages"`, which will dump a lot of details about GC activity. The 804,197,972 bytes is a fair bit smaller than the 4GB address space...

The other interesting thing about your log is that that error message comes from: https://github.com/MLton/mlton/blob/2637b22ccdd9cd1268b6b46ff6107066bf8c8888/runtime/gc/virtual-memory.c#L10-L20 and, on darwin, `GC_displayMem` is implemented as https://github.com/MLton/mlton/blob/2637b22ccdd9cd1268b6b46ff6107066bf8c8888/runtime/platform/darwin.c#L12-L17 Yet, we're not seeing the output of...