435 Commits

Author	SHA1	Message	Date
Mihai Dimoiu	70a7bbb03f	Disable component model in CI workflows and fix MSVC compile error	2026-03-30 14:34:53 +03:00
Costin Stefan	29312521d0	Reformat the code according with coding style rules.	2026-03-26 00:04:10 +02:00
Mihai Dimoiu	81cbeb2fd7	Add Component Model binary parser + validation	2026-03-25 14:53:51 +02:00
TianlongLiang	14d84eca0b	fix a wamrc compile warning, and enable system include flag for third-party libraries to suppresses corresponding compile warnings (#4875)	2026-03-19 09:08:41 +08:00
TianlongLiang	c3dda4a7d6	Fix compile error when compiler don't support '__has_feature' (#4874)	2026-03-17 16:06:45 +08:00
James Ring	c9815ef2c7	fix msan errors (#3724) ... Mark argv as initialized so that msan doesn't complain	2026-03-16 19:39:08 -07:00
Vyacheslav Chigrin	26aa924acd	Move exception lock to ModuleInstance data. (#4772) ... * Move exception lock to ModuleInstance data. This lock acquired on each native function call. This cause performance impact on programs, containing many native function calls, and running in multithreaded environment. Update AOT_CURRENT_VERSION constant.	2026-03-16 16:22:07 +08:00
liang.he	f159cc56ac	Fix: initialize record_frame in aot_copy_callstack (#4861)	2026-03-09 18:45:24 -07:00
Yi Liu	163a91b05a	Fix relocation addend sign extension on 32-bit platforms (#4846) ... * Fix relocation addend sign extension on 32-bit platforms When loading relocations on 32-bit platforms, the addend is read as uint32 and zero-extended to uint64, which corrupts negative addends. For example, -4 (0xFFFFFFFC) becomes 4294967292 instead of remaining -4. Use int32 with sign extension to int64, matching the Windows code path which already handles this correctly.	2026-03-09 10:09:28 +08:00
Yi Liu	595dcd564f	Fix off-by-one in aot_alloc_tiny_frame overflow check (#4845) ... * Fix off-by-one in aot_alloc_tiny_frame overflow check The boundary check in aot_alloc_tiny_frame only verifies that new_frame itself doesn't exceed top_boundary, but doesn't account for the sizeof(AOTTinyFrame) bytes that are about to be written. When new_frame equals top_boundary exactly, the check passes but the subsequent write to new_frame->func_index goes past the boundary. This matches the correct pattern used in aot_alloc_frame (line 4086) which includes the frame size.	2026-03-03 13:48:42 +08:00
Yi Liu	6db91d7e24	Fix off-by-one in AOT func_index bounds checks (#4836) ... The AOT relocation loader validates func_index using: (func_index = (uint32)atoi(p)) > module->func_count Since func_ptrs is an array of func_count elements (indices 0 to func_count-1), func_index == func_count is out of bounds. The check must use >= instead of > to reject this boundary case. Fix all 4 affected locations in aot_loader.c.	2026-02-13 19:21:54 +08:00
liang.he	753a348b1f	Fix a compilation error about calling os_atomic_cmpxchg (#4822) ... ``` /workspaces/wasm-micro-runtime/core/iwasm/aot/aot_runtime.c:4701:30: error: expected expression return os_atomic_cmpxchg(_Atomic(void *)ptr, &old_val, new_val); ^ /workspaces/wasm-micro-runtime/core/shared/utils/../platform/include/platform_api_extension.h:135:27: note: expanded from macro 'os_atomic_cmpxchg' ```	2026-02-03 13:56:59 +08:00
TianlongLiang	d58586a927	fix code and comment typo (#4802)	2026-01-26 14:44:47 +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
Huang Qi	b9159101cf	aot: avoid forcing mmap low addresses on NuttX (#4776) ... Signed-off-by: Huang Qi <huangqi3@xiaomi.com>	2026-01-05 10:57:18 +08:00
Krisztian	69446f4abb	Add missing functions from thumb arch (#4718) ... Signed-off-by: Krisztian Szilvasi <34309983+kr-t@users.noreply.github.com>	2025-11-28 17:08:24 +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
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	d25fdc3709	fix: typo in AOT stack dump with GC (#4657)	2025-10-16 10:20:16 +08:00
Liu Jia	d7b6bc5aca	Add a watchdog to prevent the similar crash in AOT mode (#4625)	2025-10-12 20:18:25 +08:00
Liu Jia	326eeec615	Add new cases in ARC relocation of AOT (#4653) ... * add new case for arc relocation. R_ARC_S21H_PCREL, R_ARC_S21W_PCREL	2025-10-09 11:35:12 +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
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
James Marsh	9ee44bf2d0	Add Android macro check for indirect mode	2025-08-20 13:13:56 +01:00
Liu Jia	b0dae624a1	add comments about AOT crash when calling unlinked import func (#4559)	2025-08-19 08:53:51 +08:00
Zhenwei Jin	be3f1f88fe	remove duplicate parent type index validation (#4556) ... Signed-off-by: zhenweijin <zhenwei.jin@intel.com>	2025-08-19 08:53:44 +08:00
Zhenwei Jin	ab2ff4a56d	add rec idx and rec count validation in aot loader (#4555) ... Signed-off-by: zhenweijin <zhenwei.jin@intel.com>	2025-08-19 08:53:37 +08:00
Liu Jia	cbb6d03337	add validtion for parent_type_idx (#4550)	2025-08-13 11:05:06 +08:00
TianlongLiang	d95b0e3d46	add new relocation type (#4500)	2025-08-11 15:09:33 +08:00
Zhenwei Jin	2d05aece1a	add validation for struct field type (#4536)	2025-08-11 15:07:15 +08:00
Zhenwei Jin	378320b886	loader: add type index checking (#4521)	2025-08-01 08:58:26 +08:00
Zhenwei Jin	33eff933c0	add validation for rec indices in aot loader (#4520)	2025-08-01 08:45:57 +08:00
YAMAMOTO Takashi	d298a66d38	bump AOT_CURRENT_VERSION for extended-const (#4511) ... cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/4504	2025-07-27 14:39:35 +08:00
YAMAMOTO Takashi	933e49df18	appease a few compiler warnings (-Wstrict-prototypes) (#4465)	2025-07-10 08:28:00 +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	1e41519977	loader: add type index checking (#4402)	2025-06-24 20:38:39 +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
Liu Jia	7bbdbf5212	add validation for array type in load_init_expr(GC only) (#4370)	2025-06-17 11:01:38 +08:00
TianlongLiang	0343aaf8c3	Modify AOT static PGO to conform to llvm-18 and add a CI job to test static PGO on the coremark benchmark (#4345) ... * static PGO compatible with llvm18 and add CI job to test static PGO on coremark benchmark * update comments and warning info, bitmaps section in llvm profdata shouldn't be used in PGO	2025-06-12 16:57:11 +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	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
YAMAMOTO Takashi	bb36a43fa4	riscv: avoid llvm.cttz.i32/i64 for xip (#4248) ... LLVM 16 and later expands cttz intrinsic to a table lookup, which involves some relocations. (unless ZBB is available, in which case the native instructions are preferred over the table-based lowering.) cf. https://reviews.llvm.org/D128911	2025-05-07 09:42:51 +08:00
YAMAMOTO Takashi	4735956eeb	fix return types of our 64-bit clz/ctz/popcount intrinsics (#4238) ... the corresponding LLVM intrinsics' return types are same as their first argument. eg. i64 for llvm.cttz.i64. cf. https://llvm.org/docs/LangRef.html#llvm-cttz-intrinsic this commit changes the return types of our versions of the intrinsics to match llvm versions as our aot compiler, specifically __call_llvm_intrinsic, assumes. strictly speaking, this is a potential AOT ABI change. however, I suppose it isn't a problem for many of 64-bit ABIs out there, where (lower half of) a 64-bit register is used to return a 32-bit value anyway. (for such ABIs, this commit would fix the upper 32-bit value of the register.)	2025-05-06 10:15:00 +08:00
YAMAMOTO Takashi	3232bdf2f7	teach aot emitter/loader about .srodata and .srodata.cst* sections (#4240) ... LLVM 19 and later started to use srodata ("small read only data") sections for RISCV. cf. https://github.com/llvm/llvm-project/pull/82214 this commit makes our aot emitter/loader deal with those sections. an alternative would be to disable small data sections completely by setting the "SmallDataLimit" module attribute to zero. however, i feel this commit is more straightforward and consisitent as we are already dealing with sdata sections.	2025-05-06 06:55:35 +08:00
liang.he	ecb47d9326	Add missing casts and improve error handling in performance map functions (#4202) ... Wrong type of arguments to formatting function.	2025-04-17 15:22:23 +08:00
a seven	fc78d67e15	Fix the error of AOT mode on the "i386-windows-msvc" platform (#4183) ... * Fix errors on the "i386-windows-msvc" platform * Refactor symbol name handling for AOT COFF32 binary format * Fix preprocessor directive placement for Windows compatibility in aot_reloc_x86_32.c --------- Co-authored-by: liang.he@intel.com <liang.he@intel.com>	2025-04-17 00:04:27 +08:00
liang.he	d085d1ccf7	Keep fix the CMake compatibility issue (#4180) ... ``` CMake Error at CMakeLists.txt:4 (cmake_minimum_required): Compatibility with CMake < 3.5 has been removed from CMake. Update the VERSION argument <min> value. Or, use the <min>...<max> syntax to tell CMake that the project requires at least <min> but has been updated to work with policies introduced by <max> or earlier. Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway. ```	2025-04-15 12:51:19 +08:00