wazero

Files

Takeshi Yoneda 50cef32ae0 vs: adds the benchmark to see the cost of host function calls (#756 )

This adds the new vs target to measure the cost of host function calls.
Notably, I can see that wazero is roughly 2x to 4x times faster than CGO-based
runtimes in terms of host call boundary crossing. One implication here is that
we can just focus on the native code generation rather than how to organize the
Go function calls. For example, it's not prioritized to call Go functions directly
from the native code.

Signed-off-by: Takeshi Yoneda <takeshi@tetrate.io>

2022-08-22 16:53:58 +09:00

bench

Externalize compilation cache by compilers (#747 )

2022-08-18 19:37:11 +09:00

engine

Pass context into NewRuntime (#748 )

2022-08-18 14:47:49 +09:00

filecache

Adds test to verify cross-process file system cache works (#753 )

2022-08-19 14:17:47 +09:00

Pass context into NewRuntime (#748 )

2022-08-18 14:47:49 +09:00

fuzzcases

Disallows nil context and fixes linters (#754 )

2022-08-19 14:52:50 +08:00

spectest

Adds test to verify cross-process file system cache works (#753 )

2022-08-19 14:17:47 +09:00

vs: adds the benchmark to see the cost of host function calls (#756 )

2022-08-22 16:53:58 +09:00

README.md

compiler(amd64),interpreter: signed-extend to 32-bit in V128ExtractLane. (#695 )

2022-07-14 12:47:44 +09:00

README.md

This directory contains tests which use multiple packages. For example:

bench contains benchmark tests.
engine contains variety of end-to-end tests, mainly to ensure the consistency in the behavior between engines.
fuzzcases contains variety of test cases found by wazero-fuzz.
post1_0 contains end-to-end tests for features finished after WebAssembly 1.0 (20191205).
spectest contains end-to-end tests with the WebAssembly specification tests.
vs tests and benchmarks VS other WebAssembly runtimes.

Note: This doesn't contain WASI tests, as there's not yet an official testsuite. Meanwhile, WASI functions are unit tested including via Text Format imports here