YAMAMOTO Takashi

there are a few things which we can clean up when we break AOT ABI. this issue is a reminder for them. * merge WASMModuleInstanceExtraCommon into WASModuleInstance * https://github.com/bytecodealliance/wasm-micro-runtime/blob/48b71a05fbbee26524e50a5d1df0ca77cb39e580/core/iwasm/common/wasm_shared_memory.c#L16-L17 *...

Revert "ci: Setup wasi-sdk for compilation on nuttx to fix break (#20…

2

…12)" This reverts commit 2a5a2243e3ef383221ea724234efb5237b437c11.

.github/workflows/build_wamr_lldb.yml: use a bit more specific cache key

1

the current key looks like "x86_64-ubuntu-20.04-lldb_build". it's a way too generic and can even hit the cache from the previous releases. this commit makes it contain the WAMR version number.

* implement typedef type * fall back to unspecified type

right now, wasm_set_exception propagates the trap to the whole cluster. however, when an embedder uses wasm_runtime_spawn_exec_env or wasm_runtime_spawn_thread, it depends on the use cases if the trap propagation is appropriate...

rust: trivial changes to wit definition alters the API of the generated code in an incompatible way

2

for example, ``` package foo:bar; interface hoge { variant v1 { a(u32), } set1: func(v: v1); get1: func() -> v1; variant v2 { a(u32), b(string), } set2: func(v: v2); get2:...

Exprimental WASI support for ports/unix

3

See comments in build-wasi.sh

Questions about non-atomic instructions like `i32.store`

8

when `i32.store` writes data to a shared memory, it's performed with an `wr` action. (https://webassembly.github.io/threads/core/exec/instructions.html#t-mathsf-xref-syntax-instructions-syntax-instr-memory-mathsf-store-n-xref-syntax-instructions-syntax-memarg-mathit-memarg) those events are atomically performed according to https://webassembly.github.io/threads/core/exec/runtime.html#events. thus, if a runtime implements atomic instructions...