1305 Commits

Author	SHA1	Message	Date
Wenyong Huang	c4aa1deda5	Add shared heap sample (#3806)	2024-09-20 16:13:20 +08:00
Wenyong Huang	1fd422ae6e	Merge branch main into dev/shared_heap	2024-09-20 14:34:00 +08:00
WenLY1	4dacef2d60	shared heap: Fix some issues and add basic unit test case (#3801) ... Fix some issues and add basic unit test case for shared heap feature. Signed-off-by: wenlingyun1 <wenlingyun1@xiaomi.com>	2024-09-20 14:24:38 +08:00
Anders Bakken	21330990a8	Add no_resolve to LoadArgs and wasm_runtime_resolve_symbols (#3790) ... Add no_resolve to LoadArgs and wasm_runtime_resolve_symbols so one can delay resolving of symbols. This is useful for inspecting the module between loading and instantiating.	2024-09-20 08:54:09 +08:00
Wenyong Huang	5e20cf383e	Refactor shared heap feature for interpreter mode (#3794) ... To add test cases and samples.	2024-09-18 14:53:41 +08:00
Liangyu Zhang	51a71092bf	Support dynamic aot debug (#3788) ... Enable dynamic aot debug feature which debugs the aot file and is able to set the break point and do single step. Refer to the README for the detailed steps. Signed-off-by: zhangliangyu3 <zhangliangyu3@xiaomi.com>	2024-09-18 11:02:10 +08:00
Anders Bakken	79e695e1a3	Fix a compile warning in aot_emit_function.c (#3793) ... This just fixes an unused variable warning when WASM_ENABLE_AOT_STACK_FRAME is != 0.	2024-09-18 09:37:57 +08:00
Benbuck Nason	d64a3ab6ec	Fix aot multi export memory support (#3791)	2024-09-14 10:53:01 +08:00
WenLY1	92852f3719	Implement a first version of shared heap feature (#3789) ... ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3546	2024-09-14 10:51:42 +08:00
Benbuck Nason	926f662231	Add memory instance support apis (#3786) ... Now that WAMR supports multiple memory instances, this PR adds some APIs to access them in a standard way. This involves moving some existing utility functions out from the `WASM_ENABLE_MULTI_MODULE` blocks they were nested in, but multi-memory and multi-module seem independent as far as I can tell so I assume that's okay. APIs added: ```C wasm_runtime_lookup_memory wasm_runtime_get_default_memory wasm_runtime_get_memory wasm_memory_get_cur_page_count wasm_memory_get_max_page_count wasm_memory_get_bytes_per_page wasm_memory_get_shared wasm_memory_get_base_address wasm_memory_enlarge ```	2024-09-14 10:31:13 +08:00
Marcin Kolny	9c2083a27f	Implement option for skipping function index in the callstack (#3785) ... Also add a script that converts instruction pointers to function indexes (or function names). https://github.com/bytecodealliance/wasm-micro-runtime/issues/3758	2024-09-11 16:08:37 +08:00
Benbuck Nason	c276aca202	Fix compile error when multi-module and tags are enabled (#3781)	2024-09-10 09:55:15 +08:00
YAMAMOTO Takashi	f453d9d5ce	Appease GCC strict prototypes warning (#3775)	2024-09-10 09:42:23 +08:00
Marcin Kolny	cbc2078898	AOT call stack optimizations (#3773) ... - Implement TINY / STANDARD frame modes - tiny mode is only able to keep track on the IP and func idx, STANDARD mode provides more capabilities (parameters, stack pointer etc.). - Implement FRAME_PER_FUNCTION / FRAME_PER_CALL modes - frame per function adds code at the beginning and at the end of each function for allocating / deallocating stack frame, whereas in per-call mode the frame is allocated before each call. The exception is call to the imported function, where frame-per-function mode also allocates the stack before the `call` instruction (as it can't instrument the imported function). At the moment TINY + FRAME_PER_FUNCTION is automatically enabled in case GC and perf profiling are disabled and `values` call stack feature is not requested. In all the other cases STANDARD + FRAME_PER_CALL is used. STANDARD + FRAME_PER_FUNCTION and TINY + FRAME_PER_CALL are currently not implemented but possible, and might be enabled in the future. ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3758	2024-09-10 09:05:23 +08:00
liang.he	0599351262	wasi-nn: Add a new target for llama.cpp as a wasi-nn backend (#3709) ... Minimum support: - [x] accept (WasmEdge) customized model parameters. metadata. - [x] Target [wasmedge-ggml examples](https://github.com/second-state/WasmEdge-WASINN-examples/tree/master/wasmedge-ggml) - [x] basic - [x] chatml - [x] gemma - [x] llama - [x] qwen --- In the future, to support if required: - [ ] Target [wasmedge-ggml examples](https://github.com/second-state/WasmEdge-WASINN-examples/tree/master/wasmedge-ggml) - [ ] command-r. (>70G memory requirement) - [ ] embedding. (embedding mode) - [ ] grammar. (use the grammar option to constrain the model to generate the JSON output) - [ ] llama-stream. (new APIS `compute_single`, `get_output_single`, `fini_single`) - [ ] llava. (image representation) - [ ] llava-base64-stream. (image representation) - [ ] multimodel. (image representation) - [ ] Target [llamaedge](https://github.com/LlamaEdge/LlamaEdge)	2024-09-10 08:45:18 +08:00
Marcin Kolny	6f97822c18	Add wamrc parameter to configure stack frame features (#3763) ... Those parameters can be used to reduce the size of the AOT code. There's going to be more changes related to AOT code size reduction, this is just the initial step. p.s. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3758	2024-09-05 21:44:06 +08:00
Marcin Kolny	b4380fb3b1	refactoring: Re-use commit IP functionality between exception handling and other cases (#3768)	2024-09-05 16:18:47 +08:00
Marcin Kolny	65521b188d	Remove unnecessary code duplication in aot runtime (#3767)	2024-09-05 11:10:18 +08:00
Anders Bakken	eab409a4df	aot loader: Call os_mmap with MMAP_MAP_32BIT only when target is x86-64 or riscv64 (#3755) ... Mac on aarch64 uses posix_memmap.c os_mmap which doesn't do anything with the flag MMAP_MAP_32BIT for that build so this condition ends up asserting unless the mapping ends up in the first 4 gigs worth of addressable space. Thsi PR changes to call os_mmap with MMAP_MAP_32BIT flag only when the target is x86-64 or riscv64, and the macro __APPLE__ isn't enabled. The behavior is similar to what the posix os_mmap does.	2024-08-29 15:25:17 +08:00
TianlongLiang	d1141f6f30	aot compiler: Allow to control stack boundary check when boundary check is enabled (#3754) ... In the AOT compiler, allow the user to control stack boundary check when the boundary check is enabled (e.g. `wamrc --bounds-checks=1`). Now the code logic is: 1. When `--stack-bounds-checks` is not set, it will be the same value as `--bounds-checks`. 2. When `--stack-bounds-checks` is set, it will be the option value no matter what the status of `--bounds-checks` is.	2024-08-29 11:08:39 +08:00
Anders Bakken	e8c2952bf9	Fix arm64 issues on mac (#3688) ... Make wamrc normalize "arm64" to "aarch64v8". Previously the only way to make the "arm64" target was to not specify a target on 64 bit arm-based mac builds. Now arm64 and aarch64v8 are treated as the same. Make aot_loader accept "aarch64v8" on arm-based apple (as well as accepting legacy "arm64" based aot targets). This also removes __APPLE__ and __MACH__ from the block that defaults size_level to 1 since it doesn't seem to be supported for aarch64: `LLVM ERROR: Only small, tiny and large code models are allowed on AArch64`	2024-08-23 09:49:06 +08:00
YAMAMOTO Takashi	b00904b092	Add a comment on AOT_SECTION_TYPE_SIGNATURE (#3746) ... cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3744	2024-08-22 12:35:25 +08:00
Wenyong Huang	67dce48201	Enable merged os_mmap for aot data sections and aot text (#3743) ... Enable merged os_mmap for aot data sections first, and try enabling merged os_mmap for them and aot text except on platform nuttx and esp-idf. This fixes the issue that aarch64 AOT module fails to load on android: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2274 And also refine os_mmap related code.	2024-08-21 12:55:34 +08:00
Wenyong Huang	1329e1d3e1	Add support for multi-memory proposal in classic interpreter (#3742) ... Implement multi-memory for classic-interpreter. Support core spec (and bulk memory) opcodes now, and will support atomic opcodes, and add multi-memory export APIs in the future. PS: Multi-memory spec test patched a lot for linking test to adapt for multi-module implementation.	2024-08-21 12:22:23 +08:00
Wenyong Huang	d67cc26d56	Fix load error not reported when magic header is invalid (#3734) ... When AOT isn't enabled and the input is a wasm file, wasm_runtime_load doesn't report error. Same when interpreter isn't enabled and the input is AOT file. This PR makes wasm_runtime_load report error "magic header not detected" for such situations.	2024-08-20 16:03:04 +08:00
Huang Qi	6fdad9916f	riscv: Add missing relocation intrinsics for __fixdfsi/__ltdf2 (#3733)	2024-08-20 11:06:07 +08:00
YAMAMOTO Takashi	581e1d9767	compilation: Use the dedicated stack-sizes section only for AOT (#3732) ... For JIT, we naturally use mach-o on macOS, where the section name we currently use is not valid and ends up with the errors like: ``` LLVM ERROR: Global variable '__orc_lcl.aot_stack_sizes.0' has an invalid section specifier '.aot_stack_sizes': mach-o section specifier requires a segment and section separated by a comma. ``` Because the dedicated section is not necessary for JIT, this commit simply stops using it. Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/3730	2024-08-20 10:26:26 +08:00
Wenyong Huang	97c95a2e2f	Fix table idx resolving in op call_indirect/return_call_indirect (#3726) ... The table index in the call_indirect/return_call_indirect opcode should be one byte 0x00 when ref-types/GC isn't enabled, and should be treated as leb u32 when ref-types/GC is enabled. And make aot compiler bail out if ref-types/GC is disabled by command line argument while ref-types instructions are used.	2024-08-19 10:57:36 +08:00
Huang Qi	4c127715df	aot compiler: Fix NaN handling for opcode f32/f64.const in XIP mode (#3721) ... If the value of a float constant is an NaN, the aot compiler creates an alloca, stores the converted i32 const into it and then loads f32 from it again, which may introduce a relocation in the AOT file and is not allowed for XIP mode.	2024-08-16 14:04:41 +08:00
Jan Olaf Martin	59f761b58d	aot compiler: Track non-0x00 tableindex as ref types use (#3695) ... Any use of a table index that isn't exactly a null byte (`0x00`) means that the module makes use of the reference types proposal. This is important to track because `aot_compiler.c` will blindly assume that all table indices are a single byte long otherwise. This fixes a crash in WAMR for modules that contain multi-byte encodings of table indices in `call_indirect` but make no other use of reference types features.	2024-08-16 12:37:10 +08:00
TianlongLiang	63df2cf02d	Update std atomic check and simd compatibility check for arc compiler (#3716)	2024-08-16 10:12:23 +08:00
James Ring	b845e2ede4	Add missing headers in bh_atomic.h and aot_llvm_extra.cpp (#3715)	2024-08-16 06:56:49 +08:00
Huang Qi	58ca02bc5f	Add support for RISCV32 ILP32F (#3708)	2024-08-15 15:17:42 +08:00
Wenyong Huang	740f499e9c	Fix potential memory leak in insert_native_symbol (#3712)	2024-08-14 18:11:18 +08:00
Wenyong Huang	da25906ed4	debug-interp: Only add lock when signal_flag is SIG_SINGSTEP (#3704) ... As reported in #3500, when debug interpreter is enabled, the classic interpreter performs a lock operation to read `exec_env->current_status->signal_flag` and do further handling before fetching next opcode, which makes the interpreter run slower. This PR atomic loads the `exec_env->current_status->signal_flag` without mutex lock when 32-bit atomic load is supported, and only adding lock for further handling when the signal_flag is WAMR_SIG_SINGSTEP, which improves the performance.	2024-08-14 09:03:01 +08:00
Marcin Kolny	37d7439ef9	[refactoring] Extract read leb to a separate file, share the code between loader and mini loader (#3701) ... There's probably a number of other places where the bh_leb_read could be used (e.g. aot loader) but I'm making the change as small as possible. Further refactoring can be done later.	2024-08-14 08:46:24 +08:00
Huang Qi	a83adccd20	libc-builtin: Fix function prototype for wasm_runtime_module_realloc (#3702) ... Fix: ``` wamr/core/iwasm/libraries/libc-builtin/libc_builtin_wrapper.c:20:1: warning: type of 'wasm_runtime_module_realloc' does not match original declaration [-Wlto-type-mismatch] wamr/core/iwasm/common/wasm_runtime_common.c:3033:1: note: return value type mismatch wamr/core/iwasm/common/wasm_runtime_common.c:3033:1: note: type 'uint64' should match type 'uint32' wamr/core/iwasm/common/wasm_runtime_common.c:3033:1: note: 'wasm_runtime_module_realloc' was previously declared here wamr/core/iwasm/common/wasm_runtime_common.c:3033:1: note: code may be misoptimized unless '-fno-strict-aliasing' is used ```	2024-08-13 17:44:58 +08:00
liang.he	67fa155878	libc-wasi: Make rights of STDIN/STDOUT/STDERR fixed and overlook their access modes (#3694) ... When determining the file descriptor rights in the function fd_determine_type_rights(), we assign fixed and unchangeable rights to STDIN, STDOUT and STDERR. ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3686	2024-08-13 10:10:22 +08:00
liang.he	140ff25d46	wasi-nn: Apply new architecture (#3692) ... ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3677	2024-08-13 09:14:52 +08:00
Huang Qi	c3dd5598f6	Fix a compilation warning (#3682) ... Fix: ``` wamr/core/iwasm/compilation/aot_llvm.c: In function ‘insert_native_symbol’: wamr/core/iwasm/compilation/aot_llvm.c:3290:28: warning: comparison of integer expressions of different signedness: ‘int’ and ‘long unsigned int’ [-Wsign-compare] 3290 | if (ret < 0 || ret + 1 > sizeof(sym->symbol)) { | ^ ``` Signed-off-by: Huang Qi <huangqi3@xiaomi.com>	2024-08-03 21:05:18 +08:00
dependabot[bot]	0a56abc6d6	build(deps): bump tensorflow in /core/iwasm/libraries/wasi-nn/test (#3675) ... Bumps [tensorflow](https://github.com/tensorflow/tensorflow) from 2.11.1 to 2.12.1. - [Release notes](https://github.com/tensorflow/tensorflow/releases) - [Changelog](https://github.com/tensorflow/tensorflow/blob/master/RELEASE.md) - [Commits](https://github.com/tensorflow/tensorflow/compare/v2.11.1...v2.12.1) --- updated-dependencies: - dependency-name: tensorflow dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2024-08-02 09:17:12 +08:00
Benbuck Nason	6be4b53bdf	Add emscripten_sleep() wrapper to libc-emcc (#3669)	2024-07-30 10:52:44 +08:00
dongsheng28849455	6e727dc18d	Support more features for rt-thread (#3661) ... 1, enable thread mgr 2, enable libc wasi 3, enable libc wasi threads 4, specify a function name of the module to run rather main	2024-07-26 10:34:15 +08:00
YAMAMOTO Takashi	2f147fae96	aot compiler: Bail out on too long native symbol names (#3663) ... The old code was silently truncating long names.	2024-07-25 11:38:29 +08:00
YAMAMOTO Takashi	a055e0b26f	aot compiler: Enlarge AOTNativeSymbol->symbol (#3662) ... The old value was not enough for wasm_externref_obj_to_internal_obj, which is 34 characters long.	2024-07-25 11:21:07 +08:00
Benbuck Nason	c05b93f992	aot runtime: Add missing arm/thumb relocations (#3660)	2024-07-25 11:06:41 +08:00
YAMAMOTO Takashi	d7521eea4c	libc-builtin: Fix a printf format (#3652)	2024-07-23 17:59:31 +08:00
liang.he	5e7d3ed59b	Add APIs into wasm_c_api.h to summary wasm function execution duration (#3639) ... - `wasm_instance_sum_wasm_exec_time()` -> `wasm_runtime_sum_wasm_exec_time()` - `wasm_instance_get_wasm_func_exec_time()` -> `wasm_runtime_get_wasm_func_exec_time()`	2024-07-23 16:34:47 +08:00
Benbuck Nason	b086d5820a	Change log of import function to be consistent (#3656)	2024-07-23 09:14:49 +08:00
liang.he	058bc47102	[wasi-nn] Add a new wasi-nn backend openvino (#3603)	2024-07-22 17:16:41 +08:00
YAMAMOTO Takashi	50f28495a1	Remove a few hardcoded spec test knowledge from the core library (#3648) ... Tweak the stack sizes in the spec test runner instead.	2024-07-22 13:30:00 +08:00
Wenyong Huang	8af155076c	Update version to 2.1.1 and update release notes (#3618)	2024-07-16 09:50:11 +08:00
Benbuck Nason	501d7d5adf	Add apis to get package version (#3601) ... Add three APIs: - wasm_runtime_get_file_package_version - wasm_runtime_get_module_package_version - wasm_runtime_get_current_package_version	2024-07-16 08:15:59 +08:00
HongxiaWangSSSS	7affac0ed3	wasm_application.c: Avoid null pointer dereference (#3620)	2024-07-12 16:59:59 +08:00
Wenyong Huang	73caf19e69	Fix compile warnings/error reported in Windows (#3616) ... Clear some compile warnings and fix undefined reference error for symbol ffs in Windows platform.	2024-07-12 16:43:22 +08:00
YAMAMOTO Takashi	46695b992c	EH: Use the consistent type for EH handlers (#3619) ... The "handlers" on the interpreter stack is sometimes treated as host pointers and sometimes treated as i64 values. It's quite broken for targets where pointers are not 64-bit. This commit makes them host pointers consistently. (at least for 32-bit and 64-bit pointers. We don't support other pointer sizes anyway.) Fixes https://github.com/bytecodealliance/wasm-micro-runtime/issues/3110	2024-07-12 11:00:55 +08:00
YAMAMOTO Takashi	1b1ec715e9	wasm loader: Reject v128 for interpreters (#3611) ... discussed in: https://github.com/bytecodealliance/wasm-micro-runtime/pull/3592	2024-07-10 13:50:52 +08:00
Byeongjee Kang	2cf48c8b9f	Fix typos in wamrc and wasm_export.h (#3609)	2024-07-10 12:05:58 +08:00
Benbuck Nason	8a6379bd0a	Add wasm_runtime_get_module_package_type() and wasm_runtime_get_file_package_type() (#3600) ... wasm_runtime_get_file_package_type() is the counterpart of get_file_package_type(). See discussion in #3595.	2024-07-10 10:45:19 +08:00
Benbuck Nason	8aba85825c	Avoid redefining WASMMemoryType (#3602)	2024-07-10 10:05:47 +08:00
Wenyong Huang	0feae05379	wasm loader: Fix several issues in GC and exception handling (#3586) ... Fix several issues of GC and exception handling in wasm loader: - Should restore param_reftype_maps/param_reftype_map_count/param_count in the handling of opcode throw - Should set wasm_ref_type when pushing param types of tag type and block type if the type is a multi-byte type - Should set init_values.data as NULL for opcode struct.new_default in load_init_expr This PR fixes the issues reported in #3411.	2024-07-05 19:15:58 +08:00
Wenyong Huang	1f94cd4ee5	wasm loader: Fix push_frame_offset when pushing v128 type (#3588) ... Fixes issue https://github.com/bytecodealliance/wasm-micro-runtime/issues/3580.	2024-07-03 15:18:42 +08:00
Benbuck Nason	e3074dc496	Add more arm AOT reloc entries (#3587) ... Add missing reloc entries for Arm AOT. Also sort and remove duplicate.	2024-07-03 14:44:40 +08:00
liang.he	f118492b1d	Add integer overflow check for some indices in wasm/aot loader (#3579) ... Check whether the indices overflow UINT32_MAX or not for: - import function count + function count - import global count + global count - import tag count + tag count This PR fixes the issue reported by Oss-fuzz test (#69920).	2024-07-02 15:48:37 +08:00
TianlongLiang	a5753ea920	interp debugger: Fix setting invalid value to step_count (#3583) ... The `exec_env->current_status->step_count` should be set same as the handling when WASM_ENABLE_LABELS_AS_VALUES is not 0. Fixes issue https://github.com/bytecodealliance/wasm-micro-runtime/issues/3475.	2024-07-02 11:03:49 +08:00
tonibofarull	77da87ca51	wasi-nn: Use numpy v1 in wasi-nn test requirements.txt (#3582) ... We need to fix numpy version since the latest is incompatible. > A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.0 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.	2024-07-02 09:39:46 +08:00
Benbuck Nason	837ff63662	Use 64-bit wasm_runtime_enlarge_memory() increment (#3573) ... ps. https://github.com/bytecodealliance/wasm-micro-runtime/pull/3569#discussion_r1654398315	2024-06-27 14:34:43 +08:00
liang.he	65bf04e986	aot loader: Check import global value type before using (#3571) ... Fix issue reported by Oss-fuzz test (#69798).	2024-06-26 11:19:05 +08:00
Benbuck Nason	74dbafc699	Export API wasm_runtime_enlarge_memory (#3569) ... Export API wasm_runtime_enlarge_memory to support memory growth.	2024-06-26 11:07:16 +08:00
Xenia Lu	6754b62195	Optimize for multi-module support in AOT mode (#3563) ... - Split the `aot_loader_resolve_function` into two functions to prevent redundant module lookups and loads - Access pre-associated module instances from `import_func_module_insts`, avoiding unnecessary instance lookups and improving performance	2024-06-26 09:56:01 +08:00
YAMAMOTO Takashi	867dbd8912	aot compiler: Propagate const-ness by ourselves (#3567) ... aot_load_const_from_table() hides the const-ness of the value and prevents optimizations like https://github.com/bytecodealliance/wasm-micro-runtime/pull/3552. This commit makes the aot compiler tracks the const-ness of the value directly in the AOTValue and enables the above mentioned optimization for XIP.	2024-06-25 10:57:49 +08:00
YAMAMOTO Takashi	e66b41427f	aot_resolve_target_info: Avoid in-place modification of e_type (#3564) ... * I believe that LLVM MemoryBuffer interface is supposed to be read-only and it's allowed to use eg. read-only mmap of the underlying file. It isn't appropriate to modify the view at all. * in case of WASM_ENABLE_DEBUG_AOT, the whole buffer is written as the text section of the aot file. the modified e_type would confuse dwarf consumers. note that, even when we are using XIP, the debug info usually contains relocations. for example, llvm-dwarfdump doesn't seem to perform relocations on .debug_info section for ET_CORE (== 4 == our E_TYPE_XIP) objects.	2024-06-25 10:47:23 +08:00
Xenia Lu	f7d2826772	Allow missing imports in wasm loader and report error in wasm instantiation instead (#3539) ... The wasm loader is failing when multi-module support is on and the dependent modules are not found; this enforces the AOT compiler integrations to prepare dependent modules while it isn't necessary. This PR allows allows missing imports in wasm loader and report error in wasm instantiation instead, which enables the integrated AOT compiler to work as if the multi-module support isn't turned on.	2024-06-25 10:04:39 +08:00
Xenia Lu	54b87cb097	Fix missing stack frame alloc/free in AOT multi-module invoke (#3562) ... Fix #3545 and update the build configuration for multi-module sample: - pass debug to AOT-compiled modules - support optional DUMP_CALL_STACK - support optional GC	2024-06-24 13:56:11 +08:00
liang.he	d36160b294	wasi-nn: Add wasmedge-wasinn-example as smoke test (#3554)	2024-06-24 12:03:08 +08:00
liang.he	cfffb62ad2	aot loader: Verify global value type (#3560) ... Fix issue reported by Oss-fuzz test (#69798). https://oss-fuzz.com/testcase-detail/5963842371256320	2024-06-24 10:34:03 +08:00
liang.he	95f7717555	aot loader: Add more checks in load_native_symbol_section() (#3559) ... Fix issue reported by Oss-fuzz test (#69675).	2024-06-24 10:07:10 +08:00
YAMAMOTO Takashi	4c2af25aff	aot compiler: Use larger alignment for load/store when possible (#3552) ... Consider the following wasm module: ```wast (module (func (export "foo") i32.const 0x104 i32.const 0x12345678 i32.store ) (memory 1 1) ) ``` While the address (0x104) is perfectly aligned for i32.store, as our aot compiler uses 1-byte alignment for load/store LLVM IR instructions, it often produces inefficient machine code, especially for alignment-sensitive targets. For example, the above "foo" function is compiled into the following xtensa machine code. ``` 0000002c <aot_func_internal#0>: 2c: 004136 entry a1, 32 2f: 07a182 movi a8, 0x107 32: 828a add.n a8, a2, a8 34: 291c movi.n a9, 18 36: 004892 s8i a9, a8, 0 39: 06a182 movi a8, 0x106 3c: 828a add.n a8, a2, a8 3e: ffff91 l32r a9, 3c <aot_func_internal#0+0x10> (ff91828a <aot_func_internal#0+0xff91825e>) 3e: R_XTENSA_SLOT0_OP .literal+0x8 41: 004892 s8i a9, a8, 0 44: 05a182 movi a8, 0x105 47: 828a add.n a8, a2, a8 49: ffff91 l32r a9, 48 <aot_func_internal#0+0x1c> (ffff9182 <aot_func_internal#0+0xffff9156>) 49: R_XTENSA_SLOT0_OP .literal+0xc 4c: 41a890 srli a10, a9, 8 4f: 0048a2 s8i a10, a8, 0 52: 04a182 movi a8, 0x104 55: 828a add.n a8, a2, a8 57: 004892 s8i a9, a8, 0 5a: f01d retw.n ``` Note that the each four bytes are stored separately using one-byte-store instruction, s8i. This commit tries to use larger alignments for load/store LLVM IR instructions when possible. with this commit, the above example is compiled into the following machine code, which seems more reasonable. ``` 0000002c <aot_func_internal#0>: 2c: 004136 entry a1, 32 2f: ffff81 l32r a8, 2c <aot_func_internal#0> (81004136 <aot_func_internal#0+0x8100410a>) 2f: R_XTENSA_SLOT0_OP .literal+0x8 32: 416282 s32i a8, a2, 0x104 35: f01d retw.n ``` Note: this doesn't work well for --xip because aot_load_const_from_table() hides the constness of the value. Maybe we need our own mechanism to propagate the constness and the value.	2024-06-22 10:32:52 +08:00
Benbuck Nason	e8df3b5c48	Consistent const keyword position in wasm_export.h (#3558)	2024-06-21 11:40:34 +08:00
Benbuck Nason	7d3bac62af	Add linked field comment for aot import type (#3557)	2024-06-21 10:24:56 +08:00
Wenyong Huang	9b9e938bee	Fix compilation errors (#3549) ... The compilation errors were introduced by #3515 and occur in debug building when wasm mini loader is compiled or GC is enabled. And remove two wasm files in standalone test-running-modes case, which will be generated by run.sh.	2024-06-20 12:33:52 +08:00
Florian Castellane	0418041b0d	wasm_memory.c: Fix typo: hasn't been initialize -> hasn't been initialized (#3547)	2024-06-19 17:02:09 +08:00
YAMAMOTO Takashi	a16da4f874	dwarf_extractor.cpp: Try to preserve link name (#3542) ... mainly for C++.	2024-06-19 16:51:44 +08:00
YAMAMOTO Takashi	7f94d183ac	dwarf_extractor.cpp: Fix buffer overruns (#3541) ... Probably it's better to skip the optimized out parameters. (that is, parameters w/o locations) However, I'm not sure how/if it can be done with the lldb api. For now, just disable parameter processing to avoid crashes.	2024-06-19 16:19:57 +08:00
Benbuck Nason	3746534010	Add table type API support (#3515) ... Add `wasm_runtime_get_export_table_inst` and `wasm_table_get_func_inst`, and related wasm_table_type_get_xxx APIs.	2024-06-19 14:50:46 +08:00
YAMAMOTO Takashi	72f74b7b51	dwarf_extractor.cpp: Enable limited support for C++ (#3540) ... While band-aid fixes like this is not plausible IMO, some people prefer to have some debug info even if it's partial/limited/broken. This commit partially (re)enables C++ processing. On the other hand, do not bother to process variables because it's known incompatible with C++.	2024-06-18 15:42:56 +08:00
liang.he	fa8a80a115	aot loader: Prevent loading multiple native symbol sections (#3538) ... Don't allow to load multiple native symbol sections in aot loader since the aot compiler will create only one native symbol section. Fix issue reported by Oss-fuzz test (#69633).	2024-06-18 15:31:39 +08:00
liang.he	c19bc95391	Validate func type in aot loader (#3535) ... Fix issue reported by Oss-fuzz test (#69629).	2024-06-18 14:23:32 +08:00
YAMAMOTO Takashi	f096b2fa38	wamrc: Fix truncated DW_AT_producer (#3537)	2024-06-17 18:02:12 +08:00
liang.he	db025e457a	sync up with latest wasi-nn spec (#3530)	2024-06-17 14:58:09 +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
Xenia Lu	ad5d31b9b0	Expose more functions related to emitting AOT files (#3520) ... - Add declarations related to emitting AOT files into a separate header file named `aot_emit_aot_file.h` - Add API `aot_emit_aot_file_buf_ex` and refactor `aot_emit_aot_file_buf` to call it - Expose some APIs in aot_export.h	2024-06-14 15:57:45 +08:00
liang.he	6621793acc	Fix two fuzz issues (#3529) ... - #69598: protect from `0-1` - #69608: in case no tailing `\0`	2024-06-14 15:42:21 +08:00
liang.he	f844b33b2d	Make wasi-nn backends as separated shared libraries (#3509) ... - All files under *core/iwasm/libraries/wasi-nn* are compiled as shared libraries - *wasi-nn.c* is shared between backends - Every backend has a separated shared library - If wasi-nn feature is enabled, iwasm will depend on shared library libiwasm.so instead of linking static library libvmlib.a	2024-06-14 12:06:56 +08:00
liang.he	40c41d5110	Fix several issues reported by oss-fuzz (#3526) ... - possible integer overflow in adjust_table_max_size: unsigned integer overflow: 2684354559 * 2 cannot be represented in type 'uint32' - limit max memory size in wasm_runtime_malloc - add more checks in aot loader - adjust compilation options	2024-06-13 16:06:36 +08:00
liang.he	028f43bc18	Fix compilation warnings of wasi-nn (#3497)	2024-06-07 10:49:44 +08:00
liang.he	bd44117676	Add wasi-nn example as smoke test case (#3501)	2024-06-07 10:26:09 +08:00
Benbuck Nason	5d1f19fc09	Fix wasm_mini_loader.c build when jit or multi-module is enabled (#3502) ... This PR fixes compilation error when building with `-DWAMR_BUILD_MINI_LOADER=1 -DWAMR_BUILD_JIT=1` or `-DWAMR_BUILD_MINI_LOADER=1 -DWAMR_BUILD_MULTI_MODULE=1`, though normally we don't use wasm mini loader when JIT or multi-module is enabled.	2024-06-06 09:53:22 +08:00
Benbuck Nason	8239dd4aa7	Add wasm_export.h APIs to expose memory type (#3496) ... Support to get `wasm_memory_type_t memory_type` from API `wasm_runtime_get_import_type` and `wasm_runtime_get_export_type`, and then get shared flag, initial page cout, maximum page count from the memory_type: ```C bool wasm_memory_type_get_shared(const wasm_memory_type_t memory_type); uint32_t wasm_memory_type_get_init_page_count(const wasm_memory_type_t memory_type); uint32_t wasm_memory_type_get_max_page_count(const wasm_memory_type_t memory_type); ```	2024-06-06 09:20:24 +08:00
Benbuck Nason	56b42908a8	Fix internal global getter types (#3495)	2024-06-04 11:29:31 +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
TianlongLiang	ab4e17b701	Modify logging for windows exception handler and remove unused function (#3489) ... ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3416 https://github.com/bytecodealliance/wasm-micro-runtime/issues/3400	2024-05-31 13:07:56 +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
Wenyong Huang	5623e4d22a	Fix memory64 handling find_block_addr and execute_main (#3480)	2024-05-30 16:14:12 +08:00
liang.he	d29802c451	Fix two issues to make fuzzing test quit earlier (#3471) ... - Add a marco to limit the maxi allocable memory size of fuzz test to 2GB to avoid libFuzzer out-of-memory - Check global type in load_global_import and load_global_section	2024-05-30 14:55:21 +08:00
Enrico Loparco	3b8ef89110	Clone data segments when specified with load args (#3463) ... Follow-up on https://github.com/bytecodealliance/wasm-micro-runtime/pull/3389, specifically: https://github.com/bytecodealliance/wasm-micro-runtime/pull/3389#discussion_r1600872451 If we want to free the wasm binary buffer early, we need to clone the data segments into the module. That's because, in case of [passive data segments](https://webassembly.github.io/threads/core/syntax/modules.html#syntax-data), they can be referred during wasm execution.	2024-05-27 09:59:24 +08:00
Wenyong Huang	6fdfedb08a	Fix codeql compilation error (#3461) ... Update OS to ubuntu-22.04 and install `libgcc-12-dev lib32gcc-12-dev` instead of `libgcc-11-dev lib32gcc-11-dev`. And fix a bh_assert condition typo error. ps. https://github.com/bytecodealliance/wasm-micro-runtime/actions/runs/9183310069/job/25253782329	2024-05-22 17:27:38 +08:00
Wenyong Huang	f143344842	libc-builtin: Enhance buffered print for printf_wrapper (#3460) ... Move print_buf and print_buf to str_context struct to support multi-threading when BUILTIN_LIBC_BUFFERED_PRINTF macro is enabled, and fix the issue of losing some text. ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3430.	2024-05-22 17:17:36 +08:00
Benbuck Nason	c5ab862dbb	Add api to get export global instance (#3452) ... Add API ```C bool wasm_runtime_get_export_global_inst(const wasm_module_inst_t module_inst, const char *name, wasm_global_inst_t *global_inst); ```	2024-05-22 16:59:44 +08:00
Wenyong Huang	15d191943a	Enhance GC const initializer expression to support nested struct/array new (#3447) ... Only support interpreter now, and fix some issues found in wasm loader. This PR fixes issue #3410 and #3411.	2024-05-21 16:09:12 +08:00
YAMAMOTO Takashi	403f472ff1	wasi: Tweak the configuration for nuttx and explain why (#3451)	2024-05-21 14:42:30 +08:00
TianlongLiang	30ed97cddc	Fix several typos and fix bh_log calculate mills (#3441)	2024-05-20 15:54:01 +08:00
Benbuck Nason	7744e84607	ssp_config.h: Fix ifdef for android random api (#3444) ... It looks like the preferred preprocessor check for Android is `__ANDROID__` instead of `ANDROID`: https://groups.google.com/g/android-ndk/c/cf9_f1SLXls Change `(defined(ANDROID) && __ANDROID_API__ < 28)` to `((defined(ANDROID) || defined(__ANDROID__)) && (__ANDROID_API__ < 28))`.	2024-05-18 20:23:34 +08:00
liang.he	b2eb7d838d	Update spec test to latest commit (#3293) ... - Update spec test cases to commit bc76fd79cfe61033d7f4ad4a7e8fc4f996dc5ba8 on Apr. 3 - Update wabt binary to 1.0.34 to support newer spec cases - Add comparison between table declared elem type and table elem segment value type - Add a function to decide whether to execute test cases in a running mode - Keep using interpreter in GC spec because wat2wasm in wabt can't compile if.wast w/o errors - Re-factoring threads spec test case processing - Since wabt 1.0.34 release isn't compatible with ubuntu 20.04, compile it from source code - Disable CI to run aot multi-module temporarily, and will enable it in another PR	2024-05-17 10:40:47 +08:00
Enrico Loparco	6b1d81650d	Allow not copying the wasm binary in wasm-c-api and not referring to the binary in wasm/aot loader (#3389) ... Add flag `LoadArgs.clone_wasm_binary` to control whether to clone the wasm/aot binary in wasm-c-api module. If false, API `wasm_module_new_ex` won't clone the binary, which may reduce the footprint. Add flag `LoadArgs.wasm_binary_freeable` to control whether the wasm/aot binary may be freed after instantiation for wamr API `wasm_runtime_load_ex`, if yes, then for some running modes, the wasm/aot module doesn't refer to the input binary again so developer can free it after instantiation to reduce the footprint. And add API `wasm_module_is_underlying_binary_freeable` and `wasm_runtime_is_underlying_binary_freeable` to check whether the input binary can be freed after instantiation for wasm-c-api and wamr api. And add sample to illustrate it.	2024-05-17 09:00:08 +08:00
YAMAMOTO Takashi	51ecfd6673	libc-wasi: Fix a locking botch (#3437)	2024-05-15 15:41:40 +08:00
Wenyong Huang	7949df96f4	Fix fast interp RECOVER_BR_INFO and local set/tee (#3434) ... When copying two cells from src offsets to dst offsets in RECOVER_BR_INFO, the offsets may be overlapped and the src data may be overwritten, use GET_I64_FROM_ADDR and then SET_I64_FROM_ADDR instead to resolve it. And handling VALUE_TYPE_FUNCREF/VALUE_TYPE_EXTERNREF for opcode local.set and local.tee when reference types feature is enabled. This PR fixes issue #3401 and #3402.	2024-05-15 15:20:21 +08:00
Wenyong Huang	49c9fa31da	Fix typo of WAMR_CONFIGUABLE_BOUNDS_CHECKS (#3424) ... Change to WAMR_CONFIGURABLE_BOUNDS_CHECKS, and fix CodeQL compilation errors which were introduced by PR #3406. ps. https://github.com/bytecodealliance/wasm-micro-runtime/pull/3393#discussion_r1591810998 https://github.com/bytecodealliance/wasm-micro-runtime/actions/runs/9055318553/job/24876266629	2024-05-14 14:33:09 +08:00
Benbuck Nason	0f17a1464e	Add comments to global type function declarations (#3431)	2024-05-14 11:38:18 +08:00
Wenyong Huang	773efc006d	Change WASM_ANYREF to WASM_EXTERNREF (#3426) ... wasm-c-api wasm.h had changed WASM_ANYREF to WASM_EXTERNREF, we had better change it in WAMR also: 2ce1367c9d/include/wasm.h (L185)	2024-05-14 11:08:16 +08:00
Benbuck Nason	dbd8790681	Add WASM_V128 in wasm_valkind_enum (#3412) ... Add WASM_V128 in wasm_valkind_enum and handle the the type accordingly in wasm_c_api.c and wasm_runtime_common.c, and fix a typo in V128 union.	2024-05-14 10:22:42 +08:00
YAMAMOTO Takashi	456e2f6919	aot compiler: Fix a type mismatch in compile_op_float_min_max (#3423) ... Fixes https://github.com/bytecodealliance/wasm-micro-runtime/issues/3422	2024-05-14 10:06:48 +08:00
YAMAMOTO Takashi	8f098a5905	aot: Make precheck functions use short-call for xtensa (#3418) ... Note: this breaks AOT ABI for xtensa again because of a revert of an ABI-breaking change.	2024-05-13 16:55:00 +08:00
TianlongLiang	c6d42db598	Correct Exception Handling tag type when GC is enabled (#3413) ... Use `WASMFuncType` to represent tag_type in `WASMTagImport` and `WASMTag` so that the type definition is consistent no matter to GC is enabled or not. This PR fixes https://github.com/bytecodealliance/wasm-micro-runtime/issues/3409.	2024-05-13 16:42:01 +08:00
Marcin Kolny	fe5e7a9981	Implement Memory64 support for AOT (#3362) ... Refer to: https://github.com/bytecodealliance/wasm-micro-runtime/pull/3266 https://github.com/bytecodealliance/wasm-micro-runtime/issues/3091	2024-05-13 11:03:38 +08:00
Benbuck Nason	c85bada2a9	Add wasm module global type information APIs (#3406) ... Support getting global type from `wasm_runtime_get_import_type` and `wasm_runtime_get_export_type`, and add two APIs: ```C wasm_valkind_t wasm_global_type_get_valkind(const wasm_global_type_t global_type); bool wasm_global_type_get_mutable(const wasm_global_type_t global_type); ```	2024-05-10 09:15:58 +08:00
YAMAMOTO Takashi	46f83cf486	core/iwasm/compilation: Remove stale function prototypes (#3408)	2024-05-09 16:55:32 +08:00
Wenyong Huang	a6c0cb74c9	wasm loader: Fix handling if block without op else (#3404) ... If there is no else branch, make a virtual else opcode for easier integrity check and to copy the correct results to the block return address for fast-interp mode: change if block from `if ... end` to `if ... else end`. Reported in issue #3386, #3387, #3388.	2024-05-09 16:46:26 +08:00
TianlongLiang	ea13d47a41	ref-types: Correct default value for function local variables (#3397) ... In classic interpreter, fast interpreter and fast-jit running modes, set the local variables' default value to NULL_REF (0xFFFFFFFF) rather than 0 if they are type of externref or funcref. The issue was reported in #3390 and #3391.	2024-05-09 16:31:21 +08:00
Benbuck Nason	432a940735	Fix clang compile warnings (#3396)	2024-05-08 16:43:47 +08:00
Benbuck Nason	1c2a8fca4e	Fix some more spelling issues (#3393)	2024-05-08 09:30:29 +08:00
Benbuck Nason	ca61184ced	Fix some spelling issues (#3385) ... Fix some of the spelling issues found by CSpell.	2024-05-06 07:56:48 +08:00
Benbuck Nason	c0e33f08b0	Expose API to get import/export function's param/result valkind (#3363) ... Export API: ```C wasm_func_type_get_param_count wasm_func_type_get_param_valkind wasm_func_type_get_result_count wasm_func_type_get_result_valkind ``` And change wasm_import_type/wasm_export_type to wasm_import_t/wasm_export_t.	2024-05-03 09:41:08 +08:00
Wenyong Huang	835188cc53	aot compiler: Fix the length type passed to aot_memmove/aot_memset (#3378) ... The current length type of aot_memmove/aot_memset is size_t, and on a 64 bit host it is uint64, while what the aot code passes to it is uint32, this might lead to unexpected behavior. ps. https://github.com/bytecodealliance/wasm-micro-runtime/pull/3376.	2024-05-01 21:40:52 +08:00
Benbuck Nason	4abf288c94	Fix typo for 'native' in wasm_export.h (#3376) ... Trivial spelling fix.	2024-04-30 08:57:49 +08:00
TianlongLiang	79ae910a7c	Fix loader and mini-loader select potiential error (#3374) ... Fix the issue reported in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3361.	2024-04-29 12:27:55 +08:00
Wenyong Huang	e11eae93e2	Fix aot debugger compilation error on windows (#3370) ... Fix aot debugger compilation error on windows as reported in #3184. And update the stack size configuration for product-mini zephyr sample since the native stack overflow check was enhanced and the zephyr-sdk was also upgraded.	2024-04-29 10:38:43 +08:00
YAMAMOTO Takashi	410ee580ae	Add wasm_runtime_detect_native_stack_overflow_size (#3355) ... - Add a few API (https://github.com/bytecodealliance/wasm-micro-runtime/issues/3325) ```c wasm_runtime_detect_native_stack_overflow_size wasm_runtime_detect_native_stack_overflow ``` - Adapt the runtime to use them - Adapt samples/native-stack-overflow to use them - Add a few missing overflow checks in the interpreters - Build and run the sample on the CI	2024-04-26 16:00:58 +08:00
Wenyong Huang	e44465d259	Enhance wasm loader checks for opcode br_table (#3352) ... Fix the integer overflow issue when checking target branch depth in opcode br_table, and fix is_32bit_type not check VALUE_TYPE_ANY issue, which may cause wasm_loader_push_frame_offset push extra unneeded offset.	2024-04-25 20:07:57 +08:00
YAMAMOTO Takashi	9d6d3466ff	Fix a few native stack address calculations (#3351)	2024-04-24 16:39:38 +08:00
Wenyong Huang	18d363029c	wasm loader: Fix checks for opcode ref.func and opcode else (#3340) ... Fix wasm loader integrity checks for opcode ref.func and opcode else: for opcode ref.func, the function must be an import, exported, or present in a table elem segment or global initializer to be used as the operand to ref.func, for opcode else, there must not be an else opcode previously. Reported in #3336 and #3337. And fix mini loader PUSH_MEM_OFFSET/POP_MEM_OFFSET macro definitions due to the introducing of memory64 feature.	2024-04-22 14:44:45 +08:00
Wenyong Huang	e7a8b3e743	Update version number to 2.0.0 and update release notes (#3327) ... And enable code format check for wasm_export.h and add '\n' in os_printf in sgx platform source files.	2024-04-20 10:16:34 +08:00
Benbuck Nason	8253c417a8	Add functions to expose module import/export info (#3330) ... Resolves #3329.	2024-04-20 08:57:39 +08:00
Marcin Kolny	fd7f738451	Allow executing malloc/free from native in memory64 mode (#3315)	2024-04-19 17:15:54 +08:00
Wenyong Huang	902aa525d1	Fix windows relocation string parsing issue (#3333) ... The AOT compiler emits string with '\0' now, some string parsing in aot loader for Windows platform need to be updated.	2024-04-19 16:09:03 +08:00
dongsheng28849455	ba59e56e19	User defined memory allocator for different purposes (#3316) ... Some issues are related with memory fragmentation, which may cause the linear memory cannot be allocated. In WAMR, the memory managed by the system is often trivial, but linear memory usually directly allocates a large block and often remains unchanged for a long time. Their sensitivity and contribution to fragmentation are different, which is suitable for different allocation strategies. If we can control the linear memory's allocation, do not make it from system heap, the overhead of heap management might be avoided. Add `mem_alloc_usage_t usage` as the first argument for user defined malloc/realloc/free functions when `WAMR_BUILD_ALLOC_WITH_USAGE` cmake variable is set as 1, and make passing `Alloc_For_LinearMemory` to the argument when allocating the linear memory.	2024-04-18 19:40:57 +08:00
Wenyong Huang	68bd30c6f9	Enhance GC subtyping checks (#3317) ... Enhance the GC subtyping checks: - Fix issues in the type equivalence check - Enable the recursive type subtyping check - Add a equivalence type flag in defined types of aot file, if there is an equivalence type before, just set it true and re-use the previous type - Normalize the defined types for interpreter and AOT - Enable spec test case type-equivalence.wast and type-subtyping.wast, and enable some commented cases - Enable set WAMR_BUILD_SANITIZER from cmake variable	2024-04-18 12:32:01 +08:00
liang.he	42199f163e	Log warning if growing table failed (#3310)	2024-04-15 18:29:54 +08:00
Wenyong Huang	1c690b7561	Add more checks in wasm loader (#3300) ... In opcode f32.const, f64.const and memory.copy, check whether the buffer to read is out of the range of wasm file before reading it.	2024-04-11 19:56:48 +08:00
TianlongLiang	4e634bed3f	Add necessary comments for doxygen (#3299) ... - Add necessary comments for doxygen to generate API documentation - Update README.md to add a link for End-user APIs documentation	2024-04-11 07:50:08 +08:00
liang.he	bcc2a2d2e1	Sync simd opcode definitions spec (#3290) ... Remove undefined simd opcodes.	2024-04-09 16:54:42 +08:00
Wenyong Huang	ef3babc658	interp: Restore context from prev_frame after tail calling a native function (#3283) ... The current frame was freed before tail calling to an import or native function and the prev_frame was set as exec_env's cur_frame, so after the tail calling, we should recover context from prev_frame but not current frame. Found in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3279.	2024-04-08 09:23:20 +08:00
Wenyong Huang	b11dbcba0a	thread mgr: Free aux stack only when it was allocated (#3282) ... When thread manager is enabled, the aux stack of exec_env may be allocated by wasm_cluster_allocate_aux_stack or disabled by setting aux_stack_bottom as UINTPTR_MAX directly. For the latter, no need to free it. And fix an issue when paring `--gc-heap-size=n` argument for iwasm, and fix a variable shadowed warning in fast-jit.	2024-04-08 09:06:49 +08:00
liang.he	4ef724bbff	Enhance wasm loading with LoadArgs and support module names (#3265) ... - Add new API wasm_runtime_load_ex() in wasm_export.h and wasm_module_new_ex in wasm_c_api.h - Put aot_create_perf_map() into a separated file aot_perf_map.c - In perf.map, function names include user specified module name - Enhance the script to help flamegraph generations	2024-04-07 15:04:35 +08:00
Wenyong Huang	2013f1f7d7	Fix warnings/issues reported in Windows and by CodeQL/Coverity (#3275) ... Fix the warnings and issues reported: - in Windows platform - by CodeQL static code analyzing - by Coverity static code analyzing And update CodeQL script to build exception handling and memory features.	2024-04-07 11:57:31 +08:00
YAMAMOTO Takashi	53f0941ffa	Revert "lldb_function_to_function_dbi: A hack to avoid crashing on C++ methods (#3190)" (#3281) ... This reverts commit 0e8d949440. Because it doesn't make much sense anymore after we disabled debug info processing on C++ functions in: "aot debug: process lldb_function_to_function_dbi only for C".	2024-04-06 15:00:48 +08:00
YAMAMOTO Takashi	b4cab84e5f	aot debug: Process lldb_function_to_function_dbi only for C (#3278) ... This is a workaroud for: https://github.com/bytecodealliance/wasm-micro-runtime/issues/3187 https://github.com/bytecodealliance/wasm-micro-runtime/issues/3163	2024-04-03 18:03:31 +08:00
YAMAMOTO Takashi	dae09c0e03	aot debug: Fix a NULL dereference (#3274) ... It happens on eg. a C function taking a structure argument.	2024-04-03 17:10:46 +08:00
YAMAMOTO Takashi	4806e4e298	LLVM 19: Switch to debug records (#3272) ... References: https://llvm.org/docs/RemoveDIsDebugInfo.html https://github.com/llvm/llvm-project/pull/86529	2024-04-02 16:00:43 +08:00
Wenyong Huang	a23fa9f86c	Implement memory64 for classic interpreter (#3266) ... 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 - Support memory64 memory in related runtime APIs - Modify main function type check when it's memory64 wasm file - Modify `wasm_runtime_invoke_native` and `wasm_runtime_invoke_native_raw` to handle registered native function pointer argument when memory64 is enabled - memory64 classic-interpreter spec test in `test_wamr.sh` and in CI Currently, it supports memory64 memory wasm file that uses core spec (including bulk memory proposal) opcodes and threads opcodes. ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3091 https://github.com/bytecodealliance/wasm-micro-runtime/pull/3240 https://github.com/bytecodealliance/wasm-micro-runtime/pull/3260	2024-04-02 15:22:07 +08:00
YAMAMOTO Takashi	6b0b5de1c5	aot debug: Fix a few NULL dereferences on errors (#3273)	2024-04-02 14:30:08 +08:00
dongsheng28849455	250829c0cc	Set is_vram_word_align as false in aot_const_str_set_insert function (#3271) ... Set `is_vram_word_align` as false in aot_const_str_set_insert function when `const char *name` is not from vram required word_align reading.	2024-04-02 14:17:30 +08:00
Wenyong Huang	6ee71000f9	Fix dynamic offset not updated in op_br for block with ret type (#3269) ... The PR #3259 reverted PR #3192, it fixes #3210 but makes #3170 failed again. The workaround is that we should update `ctx->dynamic_offset` only for opcode br and should not update it for opcode br_if. This PR fixes both issue #3170 and #3210.	2024-04-01 15:40:20 +08:00
Wenyong Huang	ec15b6bbad	Add lock and ref_count for runtime init (#3263) ... Some environment may call wasm_runtime_full_init/wasm_runtime_init multiple times without knowing that runtime is initialized or not, it is better to add lock and increase reference count during initialization. ps. https://github.com/bytecodealliance/wasm-micro-runtime/discussions/3253.	2024-04-01 12:39:46 +08:00
Wenyong Huang	9c8551cf75	Add cmake flag to control aot intrinsics (#3261) ... Add cmake variable `-DWAMR_BUILD_AOT_INTRINSICS=1/0` to enable/disable the aot intrinsic functions, which are normally used by AOT XIP feature, and can be disabled to reduce the aot runtime binary size. And refactor the code in aot_intrinsics.h/.c.	2024-04-01 11:26:05 +08:00
Wenyong Huang	f933d4c829	loader: Remove updating ctx->dynamic_offset in emit_br_info (#3259) ... Should not update `ctx->dynamic_offset` in emit_br_info, since the `Part e` only sets the dst offsets, the operand stack should not be changed, e.g., the stack operands are to be used by the opcodes followed by `br_if` opcode. Reported in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3210.	2024-03-28 16:07:02 +08:00
liang.he	498eb5d54a	Append \0 to every name string in aot name section (#3249) ... Since strings in .name section in .wasm is not c-style, need to append a `\0` to each string in .name section in AOT file when emitting.	2024-03-26 14:27:20 +08:00
liang.he	d8d8f8ce04	Implement apis to set and get the name of a wasm module (#3254) ... Add API wasm_runtime_set_module_name and wasm_runtime_get_module_name, and by default, a module's name is "" if the set module name api isn't called.	2024-03-26 12:10:13 +08:00
Xu Jinyang	cef88deedb	Add wasi_ephemeral_nn module support (#3241) ... Add `wasi_ephemeral_nn` module support with optional cmake variable, which was mentioned in #3229.	2024-03-21 21:05:34 +08:00
Liangyu Zhang	b11a1d157d	GC: Add wasm_struct_obj_get_field_count API (#3236)	2024-03-18 16:26:30 +08:00
Wenyong Huang	ff296c1a62	Fix aot relocation symbols not found on windows 32-bit (#3231) ... The symbols in windows 32-bit may start with '_' and can not be found when resolving the relocations to them. This PR ignores the underscore when handling the relocation name of AOT_FUNC_INTERNAL_PREFIX, and redirect the relocation with name "_aot_stack_sizes" to the relocation with name ".aot_stack_sizes" (the name of the data section created). ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3216	2024-03-18 09:51:38 +08:00
Wenyong Huang	5e2011ca1d	Fix compilation errors on esp-idf platform (#3224) ... The issue was reported in #3208.	2024-03-14 21:31:44 +08:00
TianlongLiang	de803b2beb	Small refactor on WASMModuleInstance and fix Go/Python language bindings (#3227) ... - Merge unused field `used_to_be_wasi_ctx` in `AOTModuleInstance` into `reserved` area - Add field `memory_lock` in `WASMMemoryInstance` for future refactor - Go binding: fix type error https://github.com/bytecodealliance/wasm-micro-runtime/issues/3220 - Python binding: type annotation uses the union operator "|", which requires Python version >=3.10	2024-03-14 15:30:28 +08:00
TianlongLiang	c3e33a96ea	Remove unused argument in wasm_runtime_lookup_function and refactor WASMModuleInstance (#3218) ... Remove the unused parameter `signature` from `wasm_runtime_lookup_function`. Refactor the layout of WASMModuleInstance structure: - move common data members `c_api_func_imports` and `cur_exec_env` from `WASMModuleInstanceExtraCommon` to `WASMModuleInstance` - In `WASMModuleInstance`, enlarge `reserved[3]` to `reserved[5]` in case that we need to add more fields in the future ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/2530 https://github.com/bytecodealliance/wasm-micro-runtime/issues/3202	2024-03-13 12:28:45 +08:00
Marcin Kolny	ce44e0ec0c	Allow converting the zero wasm address to native (#3215) ... This allows to know the beginning of the wasm address space. At the moment to achieve that, we need to apply a `hack wasm_runtime_addr_app_to_native(X)-X` to get the beginning of WASM memory in the nativ code, but I don't see a good reason why not to allow zero address as a parameter value for this function.	2024-03-12 17:46:11 +08:00
Wenyong Huang	0ee5ffce85	Refactor APIs and data structures as preliminary work for Memory64 (#3209) ... # Change the data type representing linear memory address from u32 to u64 ## APIs signature changes - (Export)wasm_runtime_module_malloc - wasm_module_malloc - wasm_module_malloc_internal - aot_module_malloc - aot_module_malloc_internal - wasm_runtime_module_realloc - wasm_module_realloc - wasm_module_realloc_internal - aot_module_realloc - aot_module_realloc_internal - (Export)wasm_runtime_module_free - wasm_module_free - wasm_module_free_internal - aot_module_malloc - aot_module_free_internal - (Export)wasm_runtime_module_dup_data - wasm_module_dup_data - aot_module_dup_data - (Export)wasm_runtime_validate_app_addr - (Export)wasm_runtime_validate_app_str_addr - (Export)wasm_runtime_validate_native_addr - (Export)wasm_runtime_addr_app_to_native - (Export)wasm_runtime_addr_native_to_app - (Export)wasm_runtime_get_app_addr_range - aot_set_aux_stack - aot_get_aux_stack - wasm_set_aux_stack - wasm_get_aux_stack - aot_check_app_addr_and_convert, wasm_check_app_addr_and_convert and jit_check_app_addr_and_convert - wasm_exec_env_set_aux_stack - wasm_exec_env_get_aux_stack - wasm_cluster_create_thread - wasm_cluster_allocate_aux_stack - wasm_cluster_free_aux_stack ## Data structure changes - WASMModule and AOTModule - field aux_data_end, aux_heap_base and aux_stack_bottom - WASMExecEnv - field aux_stack_boundary and aux_stack_bottom - AOTCompData - field aux_data_end, aux_heap_base and aux_stack_bottom - WASMMemoryInstance(AOTMemoryInstance) - field memory_data_size and change __padding to is_memory64 - WASMModuleInstMemConsumption - field total_size and memories_size - WASMDebugExecutionMemory - field start_offset and current_pos - WASMCluster - field stack_tops ## Components that are affected by the APIs and data structure changes - libc-builtin - libc-emcc - libc-uvwasi - libc-wasi - Python and Go Language Embedding - Interpreter Debug engine - Multi-thread: lib-pthread, wasi-threads and thread manager	2024-03-12 11:38:50 +08:00
Wenyong Huang	b6216a5f8a	Fix ip (bytecode offset) not committed into the latest aot frame (#3213)	2024-03-11 18:11:43 +08:00
Enrico Loparco	7692f32a94	Allow overriding max memory on module instantiation (#3198) ... This PR adds a max_memory_pages parameter to module instantiation APIs, to allow overriding the max memory defined in the WASM module. Sticking to the max memory defined in the module is quite limiting when using shared memory in production. If targeted devices have different memory constraints, many wasm files have to be generated with different max memory values. And device constraints may not be known in advance. Being able to set the max memory value during module instantiation allows to reuse the same wasm module, e.g. by retrying instantiation with different max memory value.	2024-03-05 17:53:26 +08:00
YAMAMOTO Takashi	0e8d949440	lldb_function_to_function_dbi: A hack to avoid crashing on C++ methods (#3190) ... Also, print the function name on argument mismatch.	2024-03-04 17:08:11 +08:00
TianlongLiang	cd63b3b8f2	Fix LLVM assertion failure and update CONTRIBUTING.md (#3197) ... The issue was reported in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3188.	2024-03-04 09:01:40 +08:00
Xu Jun	21819fcff6	Fix dynamic offset in BR for block with return type (#3192) ... The issue was reported in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3170.	2024-03-01 10:15:17 +08:00
YAMAMOTO Takashi	503c9694c8	lldb_function_to_function_dbi: Fix a null dereference (#3189) ... C++ allows unnamed arguments. In the debug info, they are represented as DW_TAG_formal_parameter w/o DW_AT_name. variable.GetName() here returns NULL for them. cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3187	2024-02-29 14:03:49 +08:00
Marcin Kolny	bc4f8ab0a5	Specify language in the wasi socket ext project (#3183) ... If the language is not specified, CMake will try to find C++ compiler, even though it is not really needed in that case (as the project is only written in C).	2024-02-28 19:35:00 +08:00
dongsheng28849455	4f6d70bc52	Use indirect call in pre-checker function to avoid relocation in XIP mode (#3142) ... The stack profiler `aot_func#xxx` calls the wrapped function of `aot_func_internal#xxx` by using symbol reference, but in some platform like xtensa, it’s translated into a native long call, which needs to resolve the indirect address by relocation and breaks the XIP feature which requires the eliminating of relocation. The solution is to change the symbol reference into an indirect call through the lookup table, the code will be like this: ```llvm call_wrapped_func: ; preds = %stack_bound_check_block %func_addr1 = getelementptr inbounds ptr, ptr %func_ptrs_ptr, i32 75 %func_tmp2 = load ptr, ptr %func_addr1, align 4 tail call void %func_tmp2(ptr %exec_env) ret void ```	2024-02-27 11:17:57 +08:00
Wenyong Huang	2349df1271	Fix ref.func opcode check when GC is enabled (#3181) ... The current code assumes that the element type of table segment can be `funcref` only, but when GC is enabled, the type can be `(ref func)` also. Fixes https://github.com/bytecodealliance/wasm-micro-runtime/issues/3168.	2024-02-27 09:31:19 +08:00
Wenyong Huang	169e164815	Fix wasm loader handling opcode br_table (#3176) ... Fix the errors reported in the sanitizer test of nightly run CI. When the stack is in polymorphic state, the stack operands may be changed after pop and push operations (e.g. stack is empty but pop op can succeed in polymorphic, and the push op can push a new operand to stack), this may impact the following checks to other target blocks of the br_table opcode.	2024-02-23 14:56:20 +08:00
Huang Qi	94db327f06	Add comments to suppress warning from wamrc (#3175)	2024-02-22 18:57:00 +08:00
Huang Qi	1429d8cc03	Fix inconsistent coding convention (#3171)	2024-02-22 10:40:50 +08:00
TianlongLiang	58c980c4df	Fix llvm jit push funcref/externref result type issue (#3169) ... When dealing with non-gc enabled funcref/externref, need to make sure to push them as i32 type.	2024-02-21 12:15:18 +08:00
Jämes Ménétrey	8b8c59589d	Clarify how to verify SGX evidence without an Intel SGX-enabled platform (#3158) ... This PR encompasses two complementing purposes: A documentation on verifying an Intel SGX evidence as produced by WAMR, including a guide for verification without an Intel SGX-enabled platform. This also contains a small addition to the RA sample to extract specific information, such as whether the enclave is running in debug mode. A C# sample to verify evidence on trusted premises (and without Intel SGX). Evidence is generated on untrusted environments, using Intel SGX.	2024-02-17 18:44:22 +08:00
Wenyong Huang	3a0e86454e	fast-interp: Fix GC opcode ref.as_non_null (#3156) ... The issue was found in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3151.	2024-02-17 11:54:49 +08:00
YAMAMOTO Takashi	b0c54c8a86	Fix a ubsan complaint "applying zero offset to null pointer" (#3160) ... Set a type's `result_ref_type_maps` only when `ref_type_map_count > 0`.	2024-02-17 10:11:10 +08:00
Marcin Kolny	e792c35822	Fix null pointer access in fast-interp when configurable soft bound check is enabled (#3150) ... The wasm_interp_call_func_bytecode is called for the first time with the empty module/exec_env to generate a global_handle_table. Before that happens though, the function checks if the module instance has bounds check enabled. Because the module instance is null, the program crashes. This PR added an extra check to prevent the crashes.	2024-02-14 17:18:37 +08:00
Xu Jun	12f834aebd	fast-interp: Fix frame_offset overflow issue (#3149) ... The issue was found in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3137.	2024-02-08 11:32:17 +08:00
Xu Jun	7cac0531ad	fast-interp: Fix copy_stack_top_i64 overlap issue (#3146) ... This fixes https://github.com/bytecodealliance/wasm-micro-runtime/issues/3145.	2024-02-07 13:24:47 +08:00
Wenyong Huang	16a4d71b34	Implement GC (Garbage Collection) feature for interpreter, AOT and LLVM-JIT (#3125) ... Implement the GC (Garbage Collection) feature for interpreter mode, AOT mode and LLVM-JIT mode, and support most features of the latest spec proposal, and also enable the stringref feature. Use `cmake -DWAMR_BUILD_GC=1/0` to enable/disable the feature, and `wamrc --enable-gc` to generate the AOT file with GC supported. And update the AOT file version from 2 to 3 since there are many AOT ABI breaks, including the changes of AOT file format, the changes of AOT module/memory instance layouts, the AOT runtime APIs for the AOT code to invoke and so on.	2024-02-06 20:47:11 +08:00
YAMAMOTO Takashi	5931aaacbe	aot compiler: Place precheck wrapper before the corresponding wrapped function (#3141) ... This increases the chance to use "short" calls. Assumptions: - LLVM preserves the order of functions in a module - The wrapper function are smaller than the wrapped functions - The target CPU has "short" PC-relative variation of call/jmp instructions and they are preferrable over the "long" ones. A motivation: - To avoid some relocations for XIP, I want to use xtensa PC-relative call instructions, which can only reach ~512KB.	2024-02-06 15:05:32 +08:00
YAMAMOTO Takashi	6e547baf46	aot_compile_op_call: Stop setting calling convention explicitly (#3140) ... The current logic doesn't work for some cases. cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3138 It's unclear why we are setting the calling convention explicitly here at all. In many cases, the default just seems working.	2024-02-06 13:14:25 +08:00
Enrico Loparco	cfa90ca44f	Use logger for runtime error/debug prints (#3097) ... Change runtime internal error/debug prints from using `os_printf()` to using `LOG_ERROR()`/`LOG_DEBUG()`.	2024-02-06 13:02:54 +08:00
TianlongLiang	f359b51525	Fix threads opcodes' boundary check in classic-interp and fast-interp (#3136) ... Using `CHECK_BULK_MEMORY_OVERFLOW(addr + offset, n, maddr)` to do the boundary check may encounter integer overflow in `addr + offset`, change to use `CHECK_MEMORY_OVERFLOW(n)` instead, which converts `addr` and `offset` to uint64 first and then add them to avoid integer overflow.	2024-02-06 11:52:30 +08:00