528 Commits

Author	SHA1	Message	Date
Yi Liu	539bebed9c	Fix missing IS_INVALID_TAGINDEX check in RETHROW handler (#4837) ... * Fix RETHROW handler missing IS_INVALID_TAGINDEX check Add validation for exception_tag_index in the RETHROW opcode handler to prevent out-of-bounds access to module->module->tags[] when the tag index is INVALID_TAGINDEX (0xFFFFFFFF). This matches the existing check in the THROW handler. When CATCH_ALL catches a cross-module exception with an unknown tag, it pushes INVALID_TAGINDEX onto the stack. Without this check, a subsequent RETHROW would access tags[0xFFFFFFFF]. * Fix incorrect code section byte counts in exception handling test The hand-crafted WASM binary in load_module_with_exception_handling had an off-by-one in the code section: body size was declared as 7 but the actual body (local count + try/catch_all/end/end) is only 6 bytes. This caused the WASM loader to fail with "unexpected end" when it tried to read past the available bytes. Fix the body size from 7 to 6 and the code section size from 9 to 8.	2026-03-09 10:04:18 +08:00
liang.he	01f4ff4cdb	workaround: prevent usage of anyref in struct fields and array elements (#4819) ... Disable corresponding cases in spec test	2026-03-03 13:05:44 +08:00
TianlongLiang	d58586a927	fix code and comment typo (#4802)	2026-01-26 14:44:47 +08:00
Zhenwei Jin	432ba8b3e0	Fix memcpy overlap issue in RECOVER_BR_INFO for i64/v128 copy (#4797) ... When copying single i64 or V128 values in RECOVER_BR_INFO, source and destination memory regions may overlap, causing memcpy-param-overlap errors Use temporary variables to separate read and write operations, preventing the overlap issue. This fix references the approach used in the other path (when arity != 1), which calls copy_stack_values, that function explicitly handles memcpy overlap. Signed-off-by: zhenweijin <zhenwei.jin@intel.com>	2026-01-26 09:59:34 +08:00
Zhenwei Jin	23df0d4e55	fix: correct boundary check in dynamic_offset check (#4788) ... correct boundary check in check_dynamic_offset_pop when dynamic_offset is 0. When dynamic_offset = 0, check_dynamic_offset_pop will always return true, which may wrongly update dynamic_offset. also include a typo fix in SET_OPERAND_REF Signed-off-by: zhenweijin <zhenwei.jin@intel.com>	2026-01-20 08:53:11 +08:00
Steven	5664589daa	fix: clear exec_env_tls when destroying exec_env (#4774) ... * fix: clear exec_env_tls when destroying exec_env When an exec_env is destroyed, check if it matches the current thread's exec_env_tls and clear it to avoid dangling pointer issues. Without this fix, in daemon-style execution where the same thread runs multiple WASM modules sequentially (like Cloudflare Workers), the exec_env_tls can point to freed memory after an exec_env is destroyed, causing crashes on subsequent executions when the signal handler tries to access it. This is critical for AOT mode with hardware bounds checking enabled, where signal handlers rely on exec_env_tls to handle SIGSEGV properly. * test(exec_env): add reproducer for exec_env_tls dangling pointer bug Add test case that reproduces the bug where exec_env_tls is not cleared on early return paths in invoke_native_with_hw_bound_check. The test triggers native stack overflow check failure, which causes wasm_runtime_call_wasm to return early after setting exec_env_tls but without clearing it. This leaves exec_env_tls pointing to a destroyed exec_env, causing subsequent calls to fail with "invalid exec env". Test confirms the fix in wasm_exec_env_destroy correctly clears exec_env_tls when destroying the exec_env it points to. * fix(runtime): clear exec_env_tls on early return from stack overflow check Move the fix to clear exec_env_tls at the source - in the early return path of invoke_native_with_hw_bound_check when native stack overflow check fails.	2026-01-20 07:09:26 +08:00
YAMAMOTO Takashi	912c2a6e31	add a set of apis to configure wasi via InstantiationArgs2 (#4707) ... * track if WASIArguments is configured by user i plan to use this to decide which wasi arguments (the one from module or the one from InstantiationArgs2) to use. * add WASIArguments to InstantiationArgs2 * use wasi configuration from InstantiationArgs2 if any fallback to the via-module configuration for now. * add a few api to configure wasi via InstantiationArgs2 * configure wasi via InstantiationArgs2 for platforms using libc_wasi.c * rt-thread: migrate to libc_wasi_set_init_args * common/libc_wasi.c: retire libc_wasi_init * fix build without wasi	2025-11-24 19:20:21 +08:00
liang.he	53ffe451d0	Fast-interp should report unsupported opcode (#4723) ... when meeting simd opcode on non-posix platforms	2025-11-24 15:48:29 +08:00
liang.he	071e2aaed5	Merge commit from fork ... * fix: remove SIMD prefix handling from interpreter and update opcode definitions * test: add case for classic interpreter handling of unsupported SIMD opcodes	2025-11-24 14:37:46 +08:00
Zhenwei Jin	33fdc4a671	Merge commit from fork	2025-11-24 14:23:04 +08:00
YAMAMOTO Takashi	3b8b265f1f	Pass InstantiationArgs2 down to aot_instantiate/wasm_instantiate (#4594) ... This is a preparation for https://github.com/bytecodealliance/wasm-micro-runtime/issues/4364 No functional changes are intended.	2025-10-23 15:57:50 +08:00
Xenia Lu	4c371e655a	fix: false OOB in array.fill for interp (#4645) ... * cherry-pick gc spec test case * Fix false OOB in array.fill	2025-10-23 13:15:42 +08:00
Liu Jia	0ecaf8c7da	add validation of dynamic_offset (#4563) ... * add check_dynamic_offset_pop	2025-10-23 11:27:30 +08:00
Xenia Lu	3bf08a0eda	loader: fix block/loop ref params type checking (#4647) ... * loader: fix block/loop ref params type checking	2025-10-16 10:20:50 +08:00
James Marsh	5ba1b331c3	Add missing condition for V128 in WASM_OP_TEE_LOCAL	2025-09-24 13:29:15 +01:00
Zhenwei Jin	e6fe6060e4	add micro AMR_BUILD_LIME1 to enable minimal lime1 feature set (#4571) ... Signed-off-by: zhenweijin <zhenwei.jin@intel.com>	2025-09-14 14:08:27 +08:00
liang.he	ad21524573	fix: few CI errors caused by recently enabled compilation flags (#4620) ... - add missing warning for incompatible pointer types in CMake configuration - fix a shadow warning	2025-09-12 16:00:23 +08:00
TianlongLiang	d7afa4c0cf	Enable -Wdouble-promotion by default and fix related warnings (#4603) ... - fix float to double implicit conversion - add isnanf and signbitf macros, map them to existing double version when float versions are absent - enable -Wdouble-promotion by default - define isnan as macro for platform use core\sahred\platform\common\math.c	2025-09-12 08:44:42 +08:00
Lukas Döllerer	0d3b5caff0	Add support for metadata.code.branch_hint section (#4460) ... Add support for metadata.code.branch_hint section	2025-09-12 08:42:48 +08:00
YAMAMOTO Takashi	6253bd1b52	Reduce the code duplication a bit (#4596) ... This is a preparation for https://github.com/bytecodealliance/wasm-micro-runtime/issues/4364 No functional changes are intended.	2025-09-04 10:58:09 +08:00
Zhenwei Jin	d55852d992	fix potential overflow in memory size calculation (#4549) ... Signed-off-by: zhenweijin <zhenwei.jin@intel.com>	2025-09-02 08:33:06 +08:00
Zhenwei Jin	feecaf602e	add bounds checking to prevent ref_type_map_count (#4548) ... Signed-off-by: zhenweijin <zhenwei.jin@intel.com>	2025-08-13 08:17:42 +08:00
Zhenwei Jin	2d05aece1a	add validation for struct field type (#4536)	2025-08-11 15:07:15 +08:00
Zhenwei Jin	aad1866260	add validation for recursive type count in loader (#4522)	2025-07-31 16:19:08 +08:00
Liu Jia	704aa3e7e5	modify macro related to simde when WASM_OP_SELECT_128 (#4461) ... * remove macro of fast interpreter when WASM_OP_SELECT_128 * Modified some macros related to SIMDE	2025-07-17 08:04:41 +08:00
Zhenwei Jin	65d3ffa7a4	add validation for recursive type count in loader (#4440)	2025-07-14 13:06:08 +08:00
Liu Jia	903a5c1f8c	improve logic of heap_type validation when ref.null (#4372) ... * Follow-up to PR #4300: prevent potential overflow PR #4300 introduced the rationale for validating heap_type. This patch moves the validation before the computation of type1 to prevent potential overflow.	2025-07-10 08:27:11 +08:00
TianlongLiang	7d05dbc988	Support extended constant expressions (#4432) ... * implement extended const expr (#4318) * add a toggle to enable extended const on wamrc (#4412)	2025-07-07 13:34:02 +08:00
TianlongLiang	8a55a1e7a1	Shared heap enhancements for Interpreter and AOT (#4400) ... Propose two enhancements: - Shared heap created from preallocated memory buffer: The user can create a shared heap from a pre-allocated buffer and see that memory region as one large chunk; there's no need to dynamically manage it(malloc/free). The user needs to make sure the native address and size of that memory region are valid. - Introduce shared heap chain: The user can create a shared heap chain, from the wasm app point of view, it's still a continuous memory region in wasm app's point of view while in the native it can consist of multiple shared heaps (each of which is a continuous memory region). For example, one 500MB shared heap 1 and one 500 MB shared heap 2 form a chain, in Wasm's point of view, it's one 1GB shared heap. After these enhancements, the data sharing between wasm apps, and between hosts can be more efficient and flexible. Admittedly shared heap management can be more complex for users, but it's similar to the zero-overhead principle. No overhead will be imposed for the users who don't use the shared heap enhancement or don't use the shared heap at all.	2025-07-04 10:44:51 +08:00
liang.he	c7148a6823	Fix potential integer overflow issues (#4429) ... It is reported as "Multiplication result converted to larger type". And "Multiplication result may overflow 'Type A' before it is converted to 'Type B'." Type A is a larger type than Type B. Since the conversion applies after the multiplication, arithmetic overflow may still occur. > The rule flags every multiplication of two non-constant integer expressions > that is (explicitly or implicitly) converted to a larger integer type. The > conversion is an indication that the expression would produce a result that > would be too large to fit in the smaller integer type.	2025-07-01 13:39:30 +08:00
Zhenwei Jin	0127eafbe5	loader: fix a potential overflow issue (#4427)	2025-06-30 12:57:57 +08:00
liang.he	0641dd1506	Fix few shadow warnings (#4409) ... - declaration of ‘memidx’ shadows a previous local - declaration of ‘count’ shadows a previous local	2025-06-27 11:55:32 +08:00
TianlongLiang	23799a2cb6	Collective fix (#4413) ... * Fix vector growth check and typos in core (#9) * Fix resource cleanup in memory and running modes tests (#10) * Add end of file empty line in wasm_running_modes_test.cc	2025-06-26 10:20:40 +08:00
Liu Jia	535004dedc	Fix handling of non-nullable global_type during global import (#4408)	2025-06-26 06:59:57 +08:00
liang.he	e414a327a0	Refactor copy callstack feature (#4401) ... - Change `WAMR_ENABLE_COPY_CALLSTACK` to `WAMR_BUILD_COPY_CALL_STACK`, as `WAMR_BUILD` is the prefix for a command line option. - Change `WAMR_ENABLE_COPY_CALLSTACK` to `WASM_ENABLE_COPY_CALL_STACK`, as `WASM_ENABLE` is the prefix for a macro in the source code. - Change `CALLSTACK` to `CALL_STACK` to align with the existing `DUMP_CALL_STACK` feature. - Continue using `WASMCApiFrame` instead of `wasm_frame_t` outside of *wasm_c_api.xxx* to avoid a typedef redefinition warning, which is identified by Clang.	2025-06-24 20:38:30 +08:00
TianlongLiang	8e60feb181	Collective fix for typos and minor bugs (#4369)	2025-06-17 09:26:00 +08:00
liang.he	75bf9797a2	Update type validation in load_table_import() and load_table() (#4296) ... Prevent from value type. https://webassembly.github.io/spec/core/valid/types.html#table-types https://webassembly.github.io/gc/core/syntax/types.html#reference-types	2025-06-12 15:01:42 +08:00
Liu Jia	928598f1ce	add heap-type check for GC when ref.null (#4300) ... - According to [Link 1](https://webassembly.github.io/gc/core/valid/instructions.html#xref-syntax-instructions-syntax-instr-ref-mathsf-ref-null-mathit-ht), we must ensure that the heap type is valid when ref.null. - According to [Link 2](https://webassembly.github.io/gc/core/valid/types.html#heap-types), a heap type is considered valid if it is either a concrete heap type or an abstract heap type. However, in this function, the check for abstract heap types (absheaptype) was clearly missing, so this condition needs to be added explicitly in the if statement. - When GC is disabled, no change is needed. - When GC is enabled, heap types in WAMR are LEB-encoded values ([Link 3](https://webassembly.github.io/gc/core/appendix/index-types.html)). Therefore, we must use read_leb_int32 to parse the heap type correctly. And we can compute the original type1 using type1 = (uint8)((int32)0x80 + heap_type);.	2025-06-12 09:31:17 +08:00
Zhenwei Jin	93ef19b0ca	handle nullable heap reference types in import section (#4302)	2025-06-03 13:28:26 +08:00
liang.he	207da7b22f	updating WASI stdio handle initialization and build options for UVWASI (#4260)	2025-05-30 07:42:39 +08:00
liang.he	7f9e49213e	Enhance type checking for function types in loader and improve error handling (#4294) ... Especially when GC is enabled, a valid item of `module->types` needs additional checks before casting to WASMFuncType. Also, avoid overflowing if reftype_map_count is 0. Additionally, correctly set IN_OSS_FUZZ based on CFLAGS_ENV for sanitizer configuration. Update ASan and UBSan messages for clarity in non-oss-fuzz environments.	2025-05-28 20:29:09 +08:00
Alix ANNERAUD	c018b8ab98	feat: Add instruction metering for interpreter (#4122) ... - add instruction metering support with execution limit - initialize instruction execution limit in exec_env - docs: add instruction metering section to build_wamr documentation	2025-05-26 16:16:42 +08:00
liang.he	e48367c044	Fix SIMD load lane to avoid incompatible pointer types (#4278)	2025-05-19 10:31:17 +08:00
Maks Litskevich	129dc3a30f	Add select 128 (#4236) ... Add select 128	2025-05-14 12:35:56 +08:00
James Ring	70b35f9e60	Check for WASM_ENABLE_SIMDE in a couple more places (#4266) ... For WAMR users who don't use cmake, it's possible that WASM_ENABLE_SIMD is set when WASM_ENABLE_SIMDE isn't. This was causing build failures.	2025-05-14 10:58:19 +08:00
liang.he	f0a8286863	Refactor fast-interpreter SIMD compilation flags (#4261) ... - enable SIMD flag by default unless hardware limitation - use SIMDE flag to control fast-interpreter behavior	2025-05-14 10:38:30 +08:00
Su Yihan	26aa4830e9	fix buf checking in load_table_section (#4276) ... Signed-off-by: Su Yihan <yihan.su@intel.com>	2025-05-14 06:35:32 +08:00
Zhenwei Jin	3cce6fdaac	avoid access null pointer (#4262)	2025-05-12 10:21:45 +08:00
YAMAMOTO Takashi	f88718d705	JIT: don't join worker threads twice (#4252) ... in case of WASM_ENABLE_LAZY_JIT==0, compile_jit_functions should have already joined these threads. joining them again here is an undefined behavior.	2025-05-08 10:24:55 +08:00
liang.he	216404d7cb	initialize WASI stdio handles to invalid for better error handling (#4092) ... * initialize WASI stdio handles to invalid for better error handling * implement os_invalid_raw_handle function for consistent invalid handle representation	2025-05-08 08:47:07 +08:00