Sam Clegg

Sorry, are you suggesting that, given and undefined external data symbol `foo`, we create global import called `foo` but we don't actually use it at anywhere? That seems even more...

Yes, llvm doesn't have any support for generating first class data or element segments, so there are no relocation types for these, and no support in the linker. If you...

Yes, there is currently no support for data.drop, elem.drop, memory.init, table.init, etc in the linkable format. We should add a "limitations" section I guess.

I think also need to figure out how we do ABI versioning in the object format before we can do something like this. I guess we could bump the version...

I don't know if calling the current ABI "whatever clang happened to implement" is fair. IIUC the current ABI was indeed developed alongside the clang/llvm work but the decision making...

Yup, looks like that docs need an update.

Hmm, I'd rather not increase the complexity that much. We had discussed a single version string, since main use case is simply to prevent linking incompatible modules. The scheme I'm...

I've been thinking about it and I think I agree with you after all :) I will update the PR. BTW I kind of like the version info being in...

My understanding is that static and dynamic linking will have the same requirements. i.e.: they both need to answer the question: "Can the code in one object inter-operate with the...

@sunfishcode does this make sense to you?