Repository navigation
docs: document --disable-memory64 in the CLI pages - #321
Merged
Merged
Conversation
The option lists for `wasmedge`, `wasmedge parse`, `wasmedge validate` and `wasmedge instantiate` covered every `--disable-*` proposal flag except `--disable-memory64`, although all of these commands accept it (registered in include/driver/options.h and shown by `--help`). The parse, validate and instantiate pages also still described Memory64 as "currently not implemented", even though it has been implemented and enabled by default since 0.17.0, as the proposals page states. Drop the stale note and add the `--disable-memory64` item after `--disable-exception-handling` on the four pages. This matches the order in options.h and the existing entry on the `wasmedge compile` page. Checked with WasmEdge 0.18.1: a module with an i64 memory runs and parses, validates and instantiates by default, and every one of these commands rejects it once `--disable-memory64` is passed. Fixes WasmEdge#319 Signed-off-by: NopeCharon <115794254+NopeCharon@users.noreply.github.com>
hydai
approved these changes
Nov 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explanation
This fixes the CLI reference pages. All
wasmedgesubcommands accept--disable-memory64, but the option lists forwasmedge,wasmedge parse,wasmedge validateandwasmedge instantiatedo not mention it. The parse, validate and instantiate pages also still call Memory64 "currently not implemented", although it has been implemented and on by default since 0.17.0.Related issue
Closes #319
What type of PR is this
/kind documentation
Proposed Changes
parse.md,validate.md,instantiate.md: drop "(currently not implemented)" from the Memory64 item under--wasm-3.cli.md,parse.md,validate.md,instantiate.md: add--disable-memory64after--disable-exception-handling. This follows the order ininclude/driver/options.hand the existing entry onaot.md.Validation with the WasmEdge 0.18.1 release (Linux aarch64), using a module that declares
(memory i64 1):--disable-memory64wasmedge --reactor m64.wasm load42loading failed: integer too largewasmedge run --reactor m64.wasm load42loading failed: integer too largewasmedge parse m64.wasmloading failed: integer too largewasmedge validate m64.wasmloading failed: integer too largewasmedge instantiate m64.wasmloading failed: integer too largenpm run buildcompletes for all locales with no warnings.