Files

Crypt Keeper 126bd9050d Removes context parameter from instruction-scoped operations (#923 )

We originally had a `context.Context` for anything that might be
traced, but it turned out to be only useful for lifecycle and host functions.

For instruction-scoped aspects like memory updates, a context parameter is too
fine-grained and also invisible in practice. For example, most users will use
the compiler engine, and its memory, global or table access will never use go's
context.

Signed-off-by: Adrian Cole <adrian@tetrate.io>

2022-12-14 16:08:07 +09:00

compiler

vs: adds the benchmark on i32/i64 load/store insts (#766 )

2022-08-26 07:32:05 +09:00

interpreter

vs: adds the benchmark on i32/i64 load/store insts (#766 )

2022-08-26 07:32:05 +09:00

testdata

vs: adds in-Wasm loop inside the memory bench (#768 )

2022-08-26 14:49:14 +09:00

time

Updates test dependencies (#834 )

2022-11-01 15:02:30 +08:00

wasmedge

Removes context parameter from instruction-scoped operations (#923 )

2022-12-14 16:08:07 +09:00

wasmer

Removes context parameter from instruction-scoped operations (#923 )

2022-12-14 16:08:07 +09:00

wasmtime

Removes context parameter from instruction-scoped operations (#923 )

2022-12-14 16:08:07 +09:00

bench_allocation.go

Removes context parameter from instruction-scoped operations (#923 )

2022-12-14 16:08:07 +09:00

bench_factorial.go

vs: adds the benchmark on i32/i64 load/store insts (#766 )

2022-08-26 07:32:05 +09:00

bench_hostcall.go

vs: adds the benchmark on i32/i64 load/store insts (#766 )

2022-08-26 07:32:05 +09:00

bench_memory.go

vs: adds in-Wasm loop inside the memory bench (#768 )

2022-08-26 14:49:14 +09:00

bench.go

Stops using "ex." to abbreviate "for example" (#827 )

2022-10-24 11:51:48 +09:00

README.md

Moves integration tests and benchmarks into one internal directory (#467 )

2022-04-15 13:33:30 +08:00

runtime.go

Removes context parameter from instruction-scoped operations (#923 )

2022-12-14 16:08:07 +09:00

README.md

VS

This directory contains tests which compare against other runtimes. As all known alternatives use CGO, this contains its own go.mod, as otherwise project dependencies are tainted and multi-platform tests more difficult to manage.

Examples of portability issues besides CGO

Wasmtime can only be used in amd64
Wasmer doesn't link on Windows