Derek Schuff

> The current DWARF for WebAssembly spec requires that instruction addresses are offsets into the Code Section. However, (extended) constant expressions contain instructions that are executed at runtime (and can...

> What happens when a constant expression evaluates to an invalid value? For example, it specifies an out-of-bounds offset for a memory segment. Maybe I've misunderstood something, but wouldn't that...

> The sections have unique integer indices (except custom sections, but that's not an issue here). DWARF has ways of using indices to specify which block of memory an instruction...

In terms of switching emscripten defaults, we need to decide when we're ready to break users on old devices with the default build, and finish getting the tools and/or documentation...

I think it does make sense in general to allow the calling convention ABI to be determined on a per-function basis, with a clang attribute you can attach to a...

Regarding the actual desired design of dynamic linking, I actually do think we are getting far enough along in the implementation where we really should start actually asking and answering...

> I think the two-level vs one-level discussion is largely separate from this one, right? i.e. I would hope that emscripten could switch to two-level namespaces without break as much...

> Performance-wise I imagine that `global.get ` would be compiled down to the same thing as `i32.const` anyway right? I that is correct assumption then really just a code size...

My initial thought is that this would be a great fit for a build ID. One of the main use cases for a build ID is associating a stripped file...

Ah, I see what you mean. Currently we have `sourceMappingURL` that serves that purpose for source maps (I think this works in Chrome?) and IIRC Chrome's DWARF extension uses a...