Petr Penzin

How to reference "full address" in presence of multiple memories. If we take only the index into memory into account there will have to be different code for different memories....

Yeah, that is what I thought. I wonder if there are any further gotchas, for example with pointers to pointers, but that might have additional restrictions w.r.t address spaces in...

> is non-default memory supposed to be accessible from languages like C at all? > as memory index is encoded as an immediate, it doesn't seem straightforward to implement "far"...

Sorry, I missed the notification somehow. > do you mean this stuff? https://en.wikipedia.org/wiki/OpenCL#Memory_hierarchy Yes, that is what I meant. LLVM supports this via addrspace annotation which works similarly to memindex...

> The component model allows a component to import a `core module` that the component internally instantiates and links with its own core client code, allowing it to share memory...

> All host-based processing of data stored in linear memory needs to change with shared memories. All loads/stores need to be atomic and additionally nothing can ever reside in the...

> **lacking toolchain support**: in the absence of any other feasible path, the WebAssembly bytes of the kernel code to be executed in parallel are embedded in the host WebAssembly...

> That's in contrast with this WASI proposal which I don't think has any path forward into the component model. Probably worth re-iterating the point @abrown made above, that this...

Just out of curiosity, as I haven't been following wasi meetings very closely, what is the background of the requirement that wasi interfaces only use component model? And does this...

@alexcrichton thank you for the detailed answers. > I'm not sure what you mean though by if this only applies to wasmtime. I meant to ask whether this is the...