SingleAccretion

Why is it important for the failure mode of the instructions (primarily `memory.map`) to be "always trap"? It limits the ability of the WASM application to handle error conditions like...

I would be in favor of keeping the debug info as well. 1) The consistency argument is a compelling one. However, with this change alone we won't achieve consistency since...

> Would you have time to send a PR? Can do that. It'll take a certain amount of setup, since one needs to get the build building, tests written and...

> like there was general agreement to go with option 1 in the short term and force the user to implement via using statements? There is no other option for...

> In any case AFAIK general practice for building portable glibc binaries is "find a super old container" ... FWIW, the dotnet/runtime version of this solution is to use a...

Doesn't the linker already support mixing object files without relocations for `call_indirect` and those with them? In other words, what would be the cost of hard-coding the indirect function table...

> The reason is that imported tables always come before defined tables in the index space Hmm, of course (obvious in retrospect :)). This also means that all object files...

> `ValidateWasiSdk`, `CompileWasmObjects` All of these targets are internal implementation details of the NAOT-LLVM build packaging. I would recommend sequencing before a more public target. For example, `IlcCompile`.

> I guess it's only using the types and macros in that file, and doesn't need any symbols at link time. That's not quite correct. We had to provide the...

I would point out that using a particular assembly format is a user-visible contract in the case of a compiler like GCC due to inline/module-level assembly (it is also the...