Use WASI instead of CommonWA

[CryZe]

CommonWA was an initial prototype of what turned into the official WASI specification. It seems like tinygo is still using CommonWA. The runtime should probably be adjusted to use WASI, with maybe an optional switch back to CommonWA, if anyone still wants to keep using that.

[aykevl]

This is something we will eventually want, certainly. The switch isn't trivial, though: we will need a bit of compiler support because wasi uses a different WebAssembly namespace and LLVM (wasm-ld?) by default puts unknown functions in the env namespace.

[CryZe]

It seems like it's just a matter of annotating the function with a "wasm-import-module" attribute in the LLVM IR. https://rust.godbolt.org/z/m0PI1z

[CryZe]

Seems like it's mostly a matter of parsing a //go:wasm-import-module xyz here

tinygo/ir/ir.go

Line 292 in da85710

case "//go:export":

and then similar to here

tinygo/compiler/compiler.go

Lines 840 to 845 in da85710

	switch frame.fn.Inline() {
	case ir.InlineHint:
	// Add LLVM inline hint to functions with //go:inline pragma.
	inline := c.ctx.CreateEnumAttribute(llvm.AttributeKindID("inlinehint"), 0)
	frame.fn.LLVMFn.AddFunctionAttr(inline)
	}

use

wasmImportModuleAttr := c.ctx.CreateStringAttribute("wasm-import-module", frame.fn.WasmImportModule)
frame.fn.LLVMFn.AddFunctionAttr(wasmImportModuleAttr)

[aykevl]

Yes, something like that will be needed.
I'm busy working on other things right now, but if you could help with such a pragma that would help.

[scriptonist]

If nobody is working on this, I can maybe give it a try :)

[CryZe]

Sure, feel free to work on it. 👍

[deadprogram]

Code that adds //go:wasm-module has now landed in the dev branch.

[deadprogram]

The //go:wasm-module directive is now part of TinyGo 0.8.0 release.

[est31]

@CryZe I wonder what's needed next.

[deadprogram]

We are using WASI now, so I think this issue can be closed. Please reopen if I am mistaken. Thanks everyone!