mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2025-12-17 09:33:03 +00:00
2c06e22d4a
Adding a new CMake flag (cache variable) `WAMR_BUILD_MEMORY64` to enable the memory64 feature, it can only be enabled on the 64-bit platform/target and can only use software boundary check. And when it is enabled, it can support both i32 and i64 linear memory types. The main modifications are: - wasm loader & mini-loader: loading and bytecode validating process - wasm runtime: memory instantiating process - classic-interpreter: wasm code executing process - memory64 classic-interpreter spec test in `test_wamr.sh` and in CI Currently, it supports memory64 memory wasm files that only use core spec (including bulk memory proposal) opcodes. Future TODOs when memory64 is enabled: 1. support threads opcodes in classic-interpreter 2. support memory64 memory in related runtime API
29 lines
744 B
Diff
29 lines
744 B
Diff
diff --git a/test/core/memory.wast b/test/core/memory.wast
|
|
index 1dd5b84..497b69f 100644
|
|
--- a/test/core/memory.wast
|
|
+++ b/test/core/memory.wast
|
|
@@ -76,17 +76,17 @@
|
|
"memory size must be at most 65536 pages (4GiB)"
|
|
)
|
|
|
|
-(assert_invalid
|
|
+(assert_malformed
|
|
(module quote "(memory 0x1_0000_0000)")
|
|
- "memory size must be at most 65536 pages (4GiB)"
|
|
+ "i32 constant out of range"
|
|
)
|
|
-(assert_invalid
|
|
+(assert_malformed
|
|
(module quote "(memory 0x1_0000_0000 0x1_0000_0000)")
|
|
- "memory size must be at most 65536 pages (4GiB)"
|
|
+ "i32 constant out of range"
|
|
)
|
|
-(assert_invalid
|
|
+(assert_malformed
|
|
(module quote "(memory 0 0x1_0000_0000)")
|
|
- "memory size must be at most 65536 pages (4GiB)"
|
|
+ "i32 constant out of range"
|
|
)
|
|
|
|
(module
|