220 Commits

Author	SHA1	Message	Date
liang.he	46472ee6c8	Enable Unit test on Mac(m1) (#4841) ... - detecting host arch. and platform instead of hard-coding - fix few compilation errors because of stricter rules involve by appleclang - refactor: modernize wasm-apps CMakeLists.txt to target-specific options and install commands - refactor: modernize memory64 CMakeLists.txt to target-specific options and install commands - Update running-modes CMakeLists.txt: enable AOT and INTERP; JIT/FAST_JIT gating for x86_64. Fix typo in JIT section. - fix: replace deprecated get_binary_path function with get_test_binary_dir for improved portability - fix: adjust size_level test cases for aarch64 architecture compatibility	2026-03-12 15:48:41 -07:00
liang.he	9e4aa9c850	fuzzing: reject non-wasm files quickly and execute aot after compilation (#4780) ... * fix: disable unsigned integer overflow sanitization in build configurations FYI: from https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html `-fsanitize=unsigned-integer-overflow`: Unsigned integer overflow, where the result of an unsigned integer computation cannot be represented in its type. Unlike signed integer overflow, this is not undefined behavior, but it is often unintentional. This sanitizer does not check for lossy implicit conversions performed before such a computation. It brings a more common question: which is better, pre-additional-check or post-additional-check to fix a potential unsigned integer overflow? A pre-additional-check involves using a check to prevent integer overflow from the very beginning. A post-additional-check involves using a check after addition to see if there is an overflow. In this project, post-additional-checking is widely used. let's follow the routine. for performance sensitive logic, use __builtin_add_overflow etc. provide something like 9a5622791e/lib/platform.h (L176-L191) and encourage the use of them. ref. https://github.com/bytecodealliance/wasm-micro-runtime/pull/4549#issuecomment-3218687294 * fix: update AOT compiler configuration and enhance error handling in fuzz tests	2026-03-09 18:24:43 -07:00
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
Ze Sheng	fe5276a155	fuzz: remove unnecessary internal headers from wasm_mutator_fuzz (#4865) ... Remove `wasm_runtime_common.h` and `bh_read_file.h` includes from the wasm_mutator_fuzz harness. All runtime APIs used by this fuzzer (wasm_runtime_init, wasm_runtime_load, wasm_runtime_instantiate, wasm_runtime_call_wasm_a, wasm_runtime_get_export_count, etc.) are declared in the public `wasm_export.h` header. - `wasm_runtime_common.h` (core/iwasm/common/) is an internal implementation header not intended for external use. - `bh_read_file.h` (core/shared/utils/uncommon/) is an internal utility header whose functions are never called in this fuzzer. Verified that the modified harness compiles and runs correctly for all three build targets (classic-interp, fast-interp, llvm-jit) with identical code coverage.	2026-03-06 21:30:29 +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
liang.he	e325a5afff	fix: update shared_heap_test to use os_getpagesize for memory size calculations (#4852)	2026-03-03 13:04:58 +08:00
liang.he	968fbbb4c9	Fix a compilation error by clang-17 (#4812) ... * Fix a compilation error by clang-17 ``` variable-sized object may not be initialized ``` clang-17 is the default version on MacOS Tahoe(26.2) on AppleM1	2026-03-03 13:04:47 +08:00
liang.he	0c9fe614ae	Improve shared_heap test cases. (#4834) ... Aligned allocation size can be significantly greater than the original size, and page size varies across platforms. > macOS on M1 (Apple Silicon) uses a memory page size of 16,384 bytes (16 KB). > This differs from the traditional 4 KB page size used on Intel Macs and many > other ARM64 systems, and is designed to improve performance by reducing page > table overhead and allowing for better cache utilization.	2026-02-15 12:45:48 +08:00
liang.he	520410d806	fix: disable unsigned integer overflow sanitization (#4785) ... * fix: disable unsigned integer overflow sanitization in build configurations FYI: from https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html `-fsanitize=unsigned-integer-overflow`: Unsigned integer overflow, where the result of an unsigned integer computation cannot be represented in its type. Unlike signed integer overflow, this is not undefined behavior, but it is often unintentional. This sanitizer does not check for lossy implicit conversions performed before such a computation. It brings a more common question: which is better, pre-additional-check or post-additional-check to fix a potential unsigned integer overflow? A pre-additional-check involves using a check to prevent integer overflow from the very beginning. A post-additional-check involves using a check after addition to see if there is an overflow. In this project, post-additional-checking is widely used. let's follow the routine. for performance sensitive logic, use __builtin_add_overflow etc. provide something like 9a5622791e/lib/platform.h (L176-L191) and encourage the use of them. ref. https://github.com/bytecodealliance/wasm-micro-runtime/pull/4549#issuecomment-3218687294 * fix: ensure proper definition checks for build options in CMakeLists of wasm-mutator * optimize how to involve sanitizer flags * fix: update LLVM branch and refine sanitizer flags in CMake configurations * fix: add requests package to development requirements	2026-01-22 05:40:52 -08:00
Steven	29767f6b51	fix(aot): reserve x18 register on macOS ARM64 (#4775) ... * fix(aot): reserve x18 register on macOS ARM64 Apple reserves CPU register x18 for TLS on ARM64. When generating AOT code for aarch64 on macOS, LLVM may use x18, causing crashes when the AOT code runs on macOS ARM64 (M1/M2/M3). This patch: 1. Detects darwin/macho ABI and sets correct vendor string 2. Detects darwin/apple in default triple for platform detection 3. Adds +reserve-x18 to LLVM target features for aarch64 on macOS The fix only applies when compiling on macOS ARM64 hosts, ensuring generated AOT code is compatible with Apple's platform requirements. * test(aot): add x18 register reservation test for macOS ARM64 Add a standalone test to verify that the +reserve-x18 LLVM flag is correctly applied when compiling AOT for macOS ARM64. On macOS ARM64, x18 is reserved by Apple for TLS (Thread Local Storage). Without the +reserve-x18 flag, LLVM may generate code that uses x18, causing random SIGSEGV crashes (~80% crash rate in testing). The test: - Creates a WASM module with 24 local variables to stress register allocation - Compiles to AOT with -O3 optimization (which would use x18 without the fix) - Runs 1000 iterations to verify no crashes occur - Only runs on macOS ARM64 (skipped on other platforms) Test results: - Without fix: 82/100 crash rate - With fix: 0/100 crash rate (1000 iterations verified)	2026-01-20 07:30:58 +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
石博文	3c337dc3ab	fix: Wrong compiler parameter on MSVC (#4778) ... * fix: Wrong compiler parameter on MSVC * refactor: Move gcc flags to common build script. * refactor: Add both C/CXX flags	2026-01-08 09:10:07 +08:00
liang.he	257d475293	update wasm-tool smith generation parameters for improved testing (#4779)	2026-01-07 11:26:27 +08:00
Zhenwei Jin	ae2fd0754b	add more unit test cases for interpreter (#4716) ... Co-authored-by: ai-assistant	2025-12-18 07:42:50 +08:00
TianlongLiang	f8448b6d79	Add a runtime API for reset shared heap(chain) (#4740) ... * add new runtime api for reset shared heap(chain) * add new unit test case	2025-12-15 09:56:55 +08:00
Zhenwei Jin	2063ac1688	enable WAMR_BUILD_MULTI_MODULE to apply all wasm-vm unit tests (#4745) ... Signed-off-by: zhenweijin <zhenwei.jin@intel.com>	2025-12-10 12:47:14 +08:00
liang.he	081c3445ef	feat: add support for checking unsupported build configurations (#4690) ... * feat: add support for checking unsupported build configurations * docs: improve clarity and formatting in build_wamr.md * feat: add check for unsupported SHARED_HEAP + FAST_JIT configuration and update documentation warning * feat: disable default SIMD setting for 64-bit platform in CMake configuration * feat: update Android and macOS workflows to handle SIMD support in classic interp mode * feat: update SGX compilation workflow to handle unsupported FAST_JIT and classic interp mode without SIMD support * feat: enhance check for unsupported CLASSIC_INTERP configurations * feat: disable fast interpreter for shared heap tests and update unsupported features test library * feat: enhance unsupported combination checks and update build configurations for JIT and SIMD * In regression tests, use llvm-jit and fast-jit to replace multi-tier-jit + running mode. Multi-tier-jit contains both fast-jit and llvm-jit. Fast-jit doesn't support SIMD, but llvm-jit does. So, should multi-tier-jit support SIMD? My answer is NO. - The regular form of multi-tier-jit uses fast-jit as tier1 and llvm-jit as tier2. Therefore, if fast-jit doesn't support SIMD, the entire multi-tier doesn't support SIMD either. - `--fast-jit` and `--llvm-jit` of multi-tier-jit should adhere to the global limitations of multi-tier-jit. * Explicitly specify SIMD, MULTI_MODULE, and their unsupported running modes. - SIMD and Ref. types are enabled by default on linux and darwin. So remove duplicate feature testing from CI - Apply new configuration for wasm-c-api compilation commands	2025-12-01 17:55:07 +08:00
liang.he	ea9e11c88f	fix: enhance test case execution handling in test_wamr.sh (#4712)	2025-12-01 17:10:52 +08:00
liang.he	a75dc9be51	Remove local fuzzing server (#4729) ... The local fuzzing server is a feature that has not been used for a long time and is currently unmaintained. Temporarily remove it from the codebase, and restore it when needed.	2025-11-25 21:02:10 +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
liang.he	a41d343033	fix: improve test case handling in test_wamr.sh (#4708) ... Correct the error introduced by de4b950.	2025-11-17 17:53:06 +08:00
TianlongLiang	7898af9f21	fix bug and add unit test case for runtime api when shared heap is enabled (#4695)	2025-11-11 16:22:45 +08:00
liang.he	de4b950781	Refactor the CMake and related scripts for unit tests (#4605) ... - only unit/CMakeLists.txt fetches googletest - only unit/unit_common.cmake find LLVM dependencies - use `WAMR_RUNTIME_LIB_SOURCE` to replace a long list - enable LLVM support across various CMake configurations - remove redundant LLVM dependency installation and add i386 support for libraries - CMake configurations for better build output and module support - Find llvm on demand - Add test suite guidelines	2025-11-04 11:44:46 +08:00
liang.he	b08b02a409	fix: update git clone branch for threads spec to main-legacy (#4687)	2025-10-31 15:40:46 +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
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
liang.he	b71a6bf58f	Turn warnings into errors in CI (#4397) ... - Apply global warnings in warnings.cmake instead of maintaining them in separate files. - Enable errors during CI when building iwasm and wamrc. - Since GCC and Clang are the default compilers on Ubuntu and macOS, enabling `-Werror` on both platforms can be treated as checking with different compilers.	2025-09-11 06:33:04 +08:00
Zhenwei Jin	e1ba1dde10	enhance WAMR_BUILD_SANITIZER to support multiple sanitizers (#4489)	2025-08-04 09:16:18 +02:00
Liu Jia	6c6447fadb	Add regression test CI (#4512) ... The entire CI test run takes approximately 3 minutes. The test run fails if there is at least one failed case (failed > 0).	2025-07-30 10:26:19 +08:00
Liu Jia	c8f7a7fc1a	fix regression running_config.json (#4477)	2025-07-14 13:08:58 +08:00
Zhenwei Jin	d6fc18e197	enable aux stack frame for aot compiler fuzz test (#4462)	2025-07-10 08:27:42 +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
Liu Jia	8949797c84	Improve run.py of regression (#4417) ... * Improve run.py of regression 1. Fix script interruption on case failure 2. improve statistics logic 3. enable select specific issue ids	2025-07-01 10:44:53 +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
liang.he	8414a20dfe	Fix several issues related to night-run CI and test scripts. (#4385) ... - remove duplicated options - fix test script - change ci to use binary	2025-06-18 19:16:47 +08:00
TianlongLiang	8e60feb181	Collective fix for typos and minor bugs (#4369)	2025-06-17 09:26:00 +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	2fe7105e8d	Update WABT downloads URL (#4357) ... Plus, skip unsupported running mode instead quit during wamr compiler test	2025-06-12 16:06:57 +08:00
liang.he	9becf65d1e	clean up incompatible running mode checks in test script and ci (#4342) ... Rearrange the content of do_execute_in_running_mode() in alphabetical order. Add an incompatible check for x86_32. Now, all belows will be bypassed: - jit, fast-jit, multi-tier-jit - memory64 - multi-memory - simd	2025-06-12 16:06:33 +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
Liu Jia	14d09bfb66	Fixed unit tests on X86_32 (#4279) ... * fix unit tests on x86_32 * enbale wasm-c-api unit test on X86_32 * enable aot-stack-frame unit test on X86_32 * add ci: unit tests on X86_32	2025-05-19 10:32:07 +08:00
Zhenwei Jin	7446b088c9	disable compiler to prevent get_current_target() crash (#4251)	2025-05-13 07:13:39 +08:00
YAMAMOTO Takashi	908838a5b5	build-scripts/build_llvm.py: bump to llvm 18 (#4259) ... * build-scripts/build_llvm.py: bump to llvm 18 cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/4210 why not 20? because, as of writing this, 19 is the latest released version for the xtensa fork of llvm: https://github.com/espressif/llvm-project why not 19? because of a bug in the xtensa fork of llvm: https://github.com/espressif/llvm-project/issues/112 while we can use different versions for different targets, it's nicer to use the same version everywhere when possible. * spec-test-script/runtest.py: --size-level=0 for x86-64 with the recent version of LLVM, wamrc --size-level=1 often generates R_X86_64_32S relocations which fail on load with the infamous error: "relocation truncated to fit R_X86_64_32S failed" it seems that these relocations are often for jump tables. this commit workarounds it with --size-level=0. an alternative is to disable jump tables. (although it seems that jump tables are not the only source of these relocations.) cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3035 it might be better to do this in wamrc itself. however, currently target info is not available there in case of native compilation. related: https://github.com/bytecodealliance/wasm-micro-runtime/issues/3356 * wamr-compiler: size_level=0 for sgx mode cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3035	2025-05-09 17:14:02 +08:00
Liu Jia	9773390537	set default value of WAMR_BUILD_REF_TYPES to 1 in standalone cases (#4227) ... - set default value of WAMR_BUILD_REF_TYPES to 1 in CMakeLists.txt	2025-04-30 14:10:56 +08:00
liang.he	a9966897b6	use a selected llvm libs list to replace the full list (#4232)	2025-04-29 11:41:34 +08:00
liang.he	1d39b9c834	bypass vptr santizier (#4231) ... LLVM, by default, disables the use of C++'s built-in Run-Time Type Information. This decision is primarily driven by concerns about code size and efficiency. But '-fsanitize=vptr' not allowed with '-fno-rtti'.	2025-04-29 10:05:02 +08:00
liang.he	791e60f533	feat(fuzz): add a new fuzzing target about aot compiler (#4121) ... support llvm-jit running mode as another fuzzing target	2025-04-28 21:44:04 +08:00