Use case
At present, Ocre supports most of the standard WebAssembly 1.0 features plus a few additional features required by the WASI-SDK/WASI-LibC toolchain. Mismatches between the WAMR runtime and the toolchain can cause issues or even failures. As such, keeping these in sync is essential. Recently, the WebAssembly adopted a convention to simplify this across runtimes and toolchains. This convention is called "Lime" (named so to align with "linear memory") and is documented here.
WAMR recently added support for building for Lime 1 (link)
Describe the solution you'd like
lime1 is the current configuration and is the default in the WASI-SDK. As such, this should be the default for Ocre so as to align with the current toolchain release.
Additional context
WASI-SDK commit making lime1 the default: WebAssembly/wasi-sdk@fbdec30
Use case
At present, Ocre supports most of the standard WebAssembly 1.0 features plus a few additional features required by the WASI-SDK/WASI-LibC toolchain. Mismatches between the WAMR runtime and the toolchain can cause issues or even failures. As such, keeping these in sync is essential. Recently, the WebAssembly adopted a convention to simplify this across runtimes and toolchains. This convention is called "Lime" (named so to align with "linear memory") and is documented here.
WAMR recently added support for building for Lime 1 (link)
Describe the solution you'd like
lime1is the current configuration and is the default in the WASI-SDK. As such, this should be the default for Ocre so as to align with the current toolchain release.Additional context
WASI-SDK commit making
lime1the default: WebAssembly/wasi-sdk@fbdec30