Sam Clegg

Do we want to include the target arch too (i.e. WASM32 vs WASM64?) Maybe not since I guess the format itself will need to have some kind of bit for...

I decided to punt on the ABI information initially and land the metadata version field first. It seems logically separate to me.

Agreed. It looks like we won't get this landed for LLVM 8.0.0 so perhaps out initial ABI can be represented a missing ABI information ?

I think the original motivation for this issue was to allow the object format itself to evolve, which is somewhat independent of the C ABI. I.e. you can imagine an...

You are correct its very useful that many tools can inspect object files. Requiring those tools to be aware of the multi-sections thing is (as far as I can tell)...

The current DLL linking that exists in emscripten (and in draft form here) does not use a two level namespace. All symbols that take part in the DLL linkable will...

Thanks for feedback, and apologies for not having better documentation in place. There is a lot of stuff to respond to here so let me know if I missed something....

@dschuff

The current scheme is that we import from the `GOT.mem` and `GOT.func` modules for data and function address. e.g. and import of `foo` from `GOT.func` is the address of function...

Yes, the current plan is it use a single stack pointer shared between all modules. For the llvm backend this means we will depend on mutable global proposal as the...