11 Commits

Author	SHA1	Message	Date
Stephen Berard	fcec30e933	Fix/branch hint parse issue (#4878) ... * test,security: added example code for invalid branch hints * security: fixes parsing issue for invalid branch_hint sections * fix: improve comments and logging in branch hint handling * feat: add support for branch hints in build configuration and documentation * test: add regression tests for invalid branch hints handling ```bash $ pwd /workspaces/wasm-micro-runtime/tests/regression/ba-issues $ ./run.py -i 980002,980003 ``` --------- Signed-off-by: Stephen Berard <stephen.berard@outlook.com> Co-authored-by: liang.he@intel.com <liang.he@intel.com>	2026-03-20 10:28:25 +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	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
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
Liu Jia	c8f7a7fc1a	fix regression running_config.json (#4477)	2025-07-14 13:08:58 +08:00
Wenyong Huang	d3e89895be	wasm loader: Fix pop invalid offset count when stack top is ANY (#3516) ... In wasm_loader_pop_frame_offset, when the stack is in polymorphic state and the stack top operand is VALUE_TYPE_ANY, if we popping I64/F64 operand, we should pop one offset but not two offsets. The issue was reported in #3513 and #3514.	2024-06-14 16:22:08 +08:00
Wenyong Huang	0a80cc4e94	Fix wasm loader check data segment count (#3492) ... When datacount section exists, loader will check whether the data count read from data segment section is same with the data count read from datacount section, but the value of latter can be 0, loader should not skip the check when the latter is 0. This fixes #3491. And fix handle_name_section return value not checked issue and early return true issue after handle_name_section. And also add the failed case in #3491 to ba-issues.	2024-06-03 19:48:11 +08:00
Wenyong Huang	23e1d51587	Fix loader parse block type and calculate dynamic offset for loop args (#3482) ... Fix several issues in wasm loader: - Parse a block's type index with leb int32 instead leb uint32 - Correct dst dynamic offset of loop block arguments for opcode br when copying the stack operands to the arguments of loop block - Free each frame_csp's param_frame_offsets when destroy loader ctx - Fix compilation error in wasm_mini_loader.c - Add test cases of failed issues This PR fixes issue #3467 and #3468.	2024-05-31 11:32:36 +08:00
Zhang, Yi	f378edc408	Add regression tests of BA issue cases (#3462)	2024-05-23 13:53:53 +08:00