Skip to content

compat.wamr: fix the interpreter named in the header comment #474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Sunrisepeak merged 1 commit into from
Sep 26, 2026
+1 −1
Merged

compat.wamr: fix the interpreter named in the header comment #474

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pkgs/c/compat.wamr.lua
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@
-- ─────────────────────────────────────────────────────────────────────────
-- WHAT THE BASE CONTAINS
--
-- Interpreter runtime only: classic + fast interpreter, bulk memory and
-- Interpreter runtime only: the fast interpreter, bulk memory and
-- reference types (both on in upstream's own default build), no AOT, no JIT,
-- and no libc for the guest. That is the configuration an embedder wants when
-- wasm modules are plugins reached only through host-provided imports.
Expand Down
Loading