1425 Commits

Author	SHA1	Message	Date
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
Xu Jun	d6d5072cc6	Fix locel.set in polymorphic stack (#3135) ... The issue was reported in #3123.	2024-02-05 17:41:33 +08:00
Wenyong Huang	b8ff98c810	Fix possible integer overflow in loader target block check (#3133) ... Checking with `loader_ctx->csp_num < depth + 1` has potential integer overflow issue when depth is UINT_MAX, change to `loader_ctx->csp_num - 1 < depth` instead. Reported in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3130.	2024-02-05 16:00:58 +08:00
Wenyong Huang	06df58f20e	Fix loader check_wasi_abi_compatibility (#3126) ... Assume that wasi exported `_start` and `_initialize` functions can not be an import function. Fixes issue #3122.	2024-02-04 17:27:43 +08:00
YAMAMOTO Takashi	529fa9dd17	EH: Fix broken stack usage calculation (#3121) ... Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/3108	2024-02-03 12:21:15 +08:00
Marcin Kolny	a27ddece7f	Always allocate linear memory using mmap (#3052) ... With this approach we can omit using memset() for the newly allocated memory therefore the physical pages are not being used unless touched by the program. This also simplifies the implementation.	2024-02-02 22:17:44 +08:00
Wenyong Huang	2eb60060d8	Fix read and validation of misc/simd/atomic sub opcodes (#3115) ... The format of sub opcodes after misc, simd and atomic prefix is leb u32. The issue was found in #2921.	2024-02-02 12:03:58 +08:00
YAMAMOTO Takashi	edc3643909	EH: Fix validation of delegate opcode (#3107) ... cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/1884#issuecomment-1914000294	2024-02-01 12:32:06 +08:00
Xu Jun	40e51faca8	fast-interp: Fix block with parameter in polymorphic stack issue (#3112) ... The issue was reported in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3061.	2024-02-01 11:55:29 +08:00
YAMAMOTO Takashi	3111a86cb3	EH: Fix delegate parsing in wasm_loader_find_block_addr (#3106)	2024-02-01 07:46:49 +08:00
YAMAMOTO Takashi	10e87d2966	EH: Don't call word_copy with zero size (#3105)	2024-01-31 21:54:19 +08:00
YAMAMOTO Takashi	43c4a5c434	exception handling: Fix build error (#3104)	2024-01-31 20:24:34 +08:00
Xu Jun	51e25ef01f	fast-interp: Fix frame_offset pop order (#3101) ... The issue was reported in #3062.	2024-01-31 19:26:27 +08:00
Xu Jun	5a99866c01	fast-interp: Fix stack recovery for else branch (#3100) ... The issue was reported in #3090.	2024-01-31 11:23:23 +08:00
Wenyong Huang	af318bac81	Implement Exception Handling for classic interpreter (#3096) ... This PR adds the initial support for WASM exception handling: * Inside the classic interpreter only: * Initial handling of Tags * Initial handling of Exceptions based on W3C Exception Proposal * Import and Export of Exceptions and Tags * Add `cmake -DWAMR_BUILD_EXCE_HANDLING=1/0` option to enable/disable the feature, and by default it is disabled * Update the wamr-test-suites scripts to test the feature * Additional CI/CD changes to validate the exception spec proposal cases Refer to: https://github.com/bytecodealliance/wasm-micro-runtime/issues/1884 587513f3c6 8bebfe9ad7 59bccdfed8 Signed-off-by: Ricardo Aguilar <ricardoaguilar@siemens.com> Co-authored-by: Chris Woods <chris.woods@siemens.com> Co-authored-by: Rene Ermler <rene.ermler@siemens.com> Co-authored-by: Trenner Thomas <trenner.thomas@siemens.com>	2024-01-31 08:27:17 +08:00
YAMAMOTO Takashi	7e65f9a244	aot: Fix LLVMSetTailCallKind check (#3099)	2024-01-30 20:50:33 +08:00
Wenyong Huang	7f8e2133ec	Fix windows build error and compilation warnings (#3095) ... Fix wamrc build error reported on Windows: ```bash CMake Error at CMakeLists.txt:84 (message): Unsupported CMAKE_HOST_SYSTEM_PROCESSOR AMD64 ``` And clear several compilation warnings.	2024-01-29 18:57:57 +08:00
liang.he	99bbad8cdb	perf profiling: Adjust the calculation of execution time (#3089)	2024-01-26 18:06:21 +08:00
Huang Qi	9fb5fcc709	Add comments to suppress warning from clang-tidy (#3088) ... Suppress style warnings for macro definition, name of these macros is inconsistent with others (upper case).	2024-01-26 17:02:24 +08:00
Wenyong Huang	313ce8cb61	Fix memory/table segment checks in memory.init/table.init (#3081) ... According to the wasm core spec, the checks for the table segments in `table.init` opcode are similar to the checks for `memory.init` opcode: - The size of a passive segment is shrunk to zero after `data.drop` (or `elem.drop`) opcode is executed, and the segment can be used to do `memory.init` (or `table.init`) again - The `memory.init` only traps when `s+n > len(data.data)` or `d+n > len(mem.data)` and `table.init` only traps when `s+n > len(elem.elem)` or `d+n > len(tab.elem)` - The active segment can also be used to do `memory.init` (or `table.init`), while it behaves like a dropped passive segment https://github.com/WebAssembly/bulk-memory-operations/blob/master/proposals/bulk-memory-operations/Overview.md ``` Segments can also be shrunk to size zero by using the following new instructions: - data.drop: discard the data in an data segment - elem.drop: discard the data in an element segment An active segment is equivalent to a passive segment, but with an implicit memory.init followed by a data.drop (or table.init followed by a elem.drop) that is prepended to the module's start function. ``` ps. https://webassembly.github.io/spec/core/bikeshed/#-hrefsyntax-instr-memorymathsfmemoryinitx%E2%91%A0 https://webassembly.github.io/spec/core/bikeshed/#-hrefsyntax-instr-tablemathsftableinitxy%E2%91%A0 https://github.com/bytecodealliance/wasm-micro-runtime/issues/3020	2024-01-26 09:45:59 +08:00
Huang Qi	6daaf6d27a	Fix inconsistent code style in aot_loader.c (#3082)	2024-01-25 17:19:14 +08:00
YAMAMOTO Takashi	9afbeab1c8	wasi: Apply wasm_runtime_begin_blocking_op to poll as well (#3080) ... While we used a different approach for poll_oneoff [1], the implementation works only when the poll list includes an absolute clock event. That is, if we have a thread which is polling on descriptors without a timeout, we fail to terminate the thread. This commit fixes it by applying wasm_runtime_begin_blocking_op to poll as well. [1] https://github.com/bytecodealliance/wasm-micro-runtime/pull/1951	2024-01-25 16:29:34 +08:00
Marcin Kolny	1505e61704	Remove a lot of "unused parameter" warnings (#3075) ... They might shadow some of the real issues, so better to keep the number of warnings as low as possible.	2024-01-24 11:21:13 +08:00
YAMAMOTO Takashi	f56154ed80	thread-mgr: Fix locking problems around aux stack allocation (#3073) ... Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/3069	2024-01-24 09:46:53 +08:00
Wenyong Huang	9f64340529	Fix some issues reported by CodeQL (#3064) ... Refer to https://github.com/bytecodealliance/wasm-micro-runtime/pull/2812 and https://github.com/bytecodealliance/wasm-micro-runtime/security/code-scanning?query=pr%3A2812+is%3Aopen	2024-01-23 21:38:30 +08:00
YAMAMOTO Takashi	ab97d543e0	wasm_cluster_destroy_spawned_exec_env: Avoid "invalid exec env" trap (#3068) ... Possible alternatives: * Make wasm_cluster_destroy_spawned_exec_env take two exec_env. One for wasm execution and another to specify the target to destroy. * Make execute functions to switch exec_env as briefly discussed in https://github.com/bytecodealliance/wasm-micro-runtime/pull/2047	2024-01-23 15:20:01 +08:00
YAMAMOTO Takashi	b44aa654b8	aot_reloc_x86_64.c: Suggest to try --size-level=0 as well (#3067) ... cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3035	2024-01-23 13:00:19 +08:00
Xu Jun	1977ad23ef	fast-interp: Fix dynamic offset error issue in else branch (#3058) ... Reported in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3026.	2024-01-19 19:58:12 +08:00
YAMAMOTO Takashi	bc35602004	Fix aot large model (--size-level=0) with LLVM 18 (#3057) ... The recent versions LLVM uses ".ltext" section for X86 large model. cf. d8a04398f9 This fixes https://github.com/bytecodealliance/wasm-micro-runtime/issues/3034	2024-01-19 19:43:41 +08:00
Wenyong Huang	ec6d9cb6be	Check arguments before calling bh_hash_map_find (#3055) ... Check whether the arguments are NULL before calling bh_hash_map_find, or lots of "HashMap find elem failed: map or key is NULL" warnings may be dumped. Reported in #3053.	2024-01-19 19:29:21 +08:00
YAMAMOTO Takashi	17b0111577	wasm_runtime_begin_blocking_op: A comment about usage expectation (#3056)	2024-01-19 18:31:21 +08:00
Wenyong Huang	a7545df5d0	classic-interp: Handle SIMD opcode when JIT is enabled (#3046) ... Though SIMD isn't supported by interpreter, when JIT is enabled, developer may run `iwasm --interp <wasm_file>` to trigger the SIMD opcode in interpreter, which isn't handled before this PR.	2024-01-19 12:31:18 +08:00
YAMAMOTO Takashi	8b37048823	Do not inherit WASM_SUSPEND_FLAG_BLOCKING from the parent thread (#3051) ... It seems that some users want to wrap rather large chunk of code with wasm_runtime_begin_blocking_op/wasm_runtime_end_blocking_op. If the wrapped code happens to have a call to e.g. wasm_runtime_spawn_exec_env, WASM_SUSPEND_FLAG_BLOCKING is inherited to the child exec_env and it may cause unexpected behaviors.	2024-01-19 09:55:01 +08:00
Wenyong Huang	9bcf6b4dd3	Enable quick aot entry when hw bound check is disabled (#3044) ... - Enable quick aot entry when hw bound check is disabled - Remove unnecessary ret_type argument in the quick aot entries - Declare detailed prototype of aot function to call in each quick aot entry	2024-01-19 08:55:35 +08:00
tkernelcn	a9807058a6	Set CONFIG_HAS_CAP_ENTER to support posix file api for freertos (#3041) ... Since there is no so rich api in freertos like embedded system, simply set CONFIG_HAS_CAP_ENTER to 1 to support posix file api for freertos. Test file api in wasm app pass.	2024-01-17 21:20:35 +08:00
liang.he	5c8b8a17a6	Enhancements on wasm function execution time statistic (#2985) ... Enhance the statistic of wasm function execution time, or the performance profiling feature: - Add os_time_thread_cputime_us() to get the cputime of a thread, and use it to calculate the execution time of a wasm function - Support the statistic of the children execution time of a function, and dump it in wasm_runtime_dump_perf_profiling - Expose two APIs: wasm_runtime_sum_wasm_exec_time wasm_runtime_get_wasm_func_exec_time And rename os_time_get_boot_microsecond to os_time_get_boot_us.	2024-01-17 09:51:54 +08:00
Marcin Kolny	ffa131b5ac	Allow using mmap for shared memory if hw bound check is disabled (#3029) ... For shared memory, the max memory size must be defined in advanced. Re-allocation for growing memory can't be used as it might change the base address, therefore when OS_ENABLE_HW_BOUND_CHECK is enabled the memory is mmaped, and if the flag is disabled, the memory is allocated. This change introduces a flag that allows users to use mmap for reserving memory address space even if the OS_ENABLE_HW_BOUND_CHECK is disabled.	2024-01-16 22:15:55 +08:00
Wenyong Huang	b3aaf2abc0	Check passive mode in fast-jit table.init (#3031) ... Reported in https://github.com/bytecodealliance/wasm-micro-runtime/issues/3021.	2024-01-16 21:55:10 +08:00
Huang Qi	915adc433d	Rename rwlock_init to avoid conflict (#3016) ... This symbol is too simple to cause conflict with others, such as the RW spinlock in Linux kernel and NuttX, so rename it to avoid the conflict.	2024-01-16 08:53:18 +08:00
Enrico Loparco	892a94fd05	fix(wasm-c-api): Do not clone stack frames if there's no trap (#3008) ... When running the wasi-threads no_pthread sample, the assert was failing on `src->num_elems != 0` in debug mode, it is because that the exception is `proc_exit`, there is no trap (the execution didn't fail, no stack frames): https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/samples/wasi-threads/wasm-apps/no_pthread.c	2024-01-15 18:18:37 +08:00
YAMAMOTO Takashi	837b9904f5	aot debug: Try to use a bit more appropriate file names (#3000) ... When the original wasm contains multiple compilation units, the current logic uses the first one for everything. This commit tries to use a bit more appropriate ones.	2024-01-15 15:02:12 +08:00
Wenyong Huang	23d2e0627c	Clear compilation warning and dead code (#3002)	2024-01-13 08:56:39 +08:00
Maks Litskevich	63012f0222	Fix build errors when initializing wasm_val_t values with macros (#3007) ... Errors were reported when initializing wasm_val_t values with WASM_I32_VAL like macros. ``` error: missing initializer for member ‘wasm_val_t::__paddings’ [-Werror=missing-field-initializers] 64 | wasm_val_t res = {WASM_INIT_VAL}; ``` And rename DEPRECATED to WASM_API_DEPRECATED to avoid using defines with generic names.	2024-01-13 08:35:49 +08:00
YAMAMOTO Takashi	08442458b1	aot debug: Update DW_AT_producer (#3001) ... Currently we are using "ant compiler", which is a bit historical. This commit changes it to use "WAMR AoT compiler" instead.	2024-01-12 13:43:18 +08:00
liang.he	9121db5671	Fix a bug when emit the custom name section to aot file (#2987) ... The content in custom name section is changed after loaded since the strings are adjusted with '\0' appended, the emitted AOT file then cannot be loaded. The PR disables changing the content for AOT compiler to resolve it. And disable emitting custom name section for `wamrc --enable-dump-call-stack`, instead, use `wamrc --emit-custom-sections=name` to emit it.	2024-01-11 13:14:54 +08:00
Enrico Loparco	ff25110840	Return stack frames of crashed thread when using wasm-c-api (#2908) ... When using the wasm-c-api and there's a trap, `wasm_func_call()` returns a `wasm_trap_t *` object. No matter which thread crashes, the trap contains the stack frames of the main thread. With this PR, when there's an exception, the stack frames of the thread where the exception occurs are stored into the thread cluster. `wasm_func_call()` can then return those stack frames.	2024-01-11 12:13:05 +08:00
Wenyong Huang	b21f17dd6d	Refine AOT/JIT code call wasm-c-api import process (#2982) ... Allow to invoke the quick call entry wasm_runtime_quick_invoke_c_api_import to call the wasm-c-api import functions to speedup the calling process, which reduces the data copying. Use `wamrc --invoke-c-api-import` to generate the optimized AOT code, and set `jit_options->quick_invoke_c_api_import` true in wasm_engine_new when LLVM JIT is enabled.	2024-01-10 18:37:02 +08:00
Wenyong Huang	7c7684819d	Register quick call entries to speedup the aot/jit func call process (#2978) ... In some scenarios there may be lots of callings to AOT/JIT functions from the host embedder, which expects good performance for the calling process, while in the current implementation, runtime calls the wasm_runtime_invoke_native to prepare the array of registers and stacks for the invokeNative assemble code, and the latter then puts the elements in the array to physical registers and native stacks and calls the AOT/JIT function, there may be many data copying and handlings which impact the performance. This PR registers some quick AOT/JIT entries for some simple wasm signatures, and let runtime call the entry to directly invoke the AOT/JIT function instead of calling wasm_runtime_invoke_native, which speedups the calling process. We may extend the mechanism next to allow the developer to register his quick AOT/JIT entries to speedup the calling process of invoking the AOT/JIT functions for some specific signatures.	2024-01-10 16:44:09 +08:00
YAMAMOTO Takashi	722381fcf2	aot compiler: Some updates for LLVM 18 (#2981) ... Note: This commit includes copy-and-paste from LLVM and thus adds the LLVM copyright notice. cf. 0a1aa6cda2 cf. a1e9777b76 cf. 56c72c7f33	2024-01-08 10:15:31 +08:00
Wenyong Huang	c39214e8a5	Fix potential recursive lock in pthread_create_wrapper (#2980) ... Potential recursive lock occurs in: ``` pthread_create_wrapper (acquire exec_env->wait_lock) => wasm_cluster_create_thread => allocate_aux_stack => wasm_runtime_module_malloc_internal => wasm_call_function => wasm_exec_env_set_thread_info (acquire exec_env->wait_lock again) ``` Allocate aux stack before calling wasm_cluster_create_thread to resolve it. Reported in https://github.com/bytecodealliance/wasm-micro-runtime/pull/2977.	2024-01-08 09:43:31 +08:00
tkernelcn	4a1ad9a160	freertos: Change ssp_config.h due to clock_nanosleep() not supported in freertos (#2979)	2024-01-04 20:01:54 +08:00
Xu Jun	f96257bade	Fix fast-interp polymorphic stack processing (#2974) ... Fix issue #2951, #2952 and #2953.	2024-01-04 10:00:36 +08:00
tkernelcn	a2751903ff	freertos: Minor changes for freertos libc_wasi build adaption (#2973)	2024-01-04 09:49:24 +08:00
Wenyong Huang	1ee4767d97	Fix ref.func function declared check in wasm loader (#2972) ... The forward-declare function reference in ref.func can be declared in table element segments, no matter whether the segment mode is passive, active or declarative. Reported in https://github.com/bytecodealliance/wasm-micro-runtime/issues/2944.	2024-01-03 11:43:03 +08:00
liutao	75a2b98eb4	simd-128: The input lanes of integer-to-integer narrowing ops should be interpreted as signed (#2850) ... https://github.com/WebAssembly/spec/blob/main/proposals/simd/SIMD.md#integer-to-integer-narrowing	2024-01-03 09:51:58 +08:00
Wenyong Huang	c43e4505da	Allow to set segue flags for wasm-c-api JIT (#2926) ... Add an API to set segue flags for wasm-c-api LLVM JIT mode: ```C wasm_config_t * wasm_config_set_segue_flags(wasm_config_t *config, uint32 segue_flags); ```	2024-01-02 19:34:18 +08:00
Wenyong Huang	aa4d68c2af	Refine AOT function call process (#2940) ... Don't set exec_env's thread handle and stack boundary in the recursive calling from host, since they have been initialized in the first time calling.	2024-01-02 19:10:31 +08:00
Wenyong Huang	3637f2df79	Refine LLVM JIT function call process (#2925) ... - Don't allocate the implicit/unused frame when calling the LLVM JIT function - Don't set exec_env's thread handle and stack boundary in the recursive calling from host, since they have been set in the first time calling - Fix frame not freed in llvm_jit_call_func_bytecode	2024-01-02 18:46:02 +08:00
Xu Jun	d818672f62	Fix ref.is_null processing in fast-interp loader (#2971)	2024-01-02 18:10:01 +08:00
Wenyong Huang	2ee013faf3	fast-jit: Fix const shift and const i64 compare issues (#2969)	2024-01-02 17:56:34 +08:00
liang.he	5c3ad0279a	Enable AOT linux perf support (#2930) ... And refactor the original perf support - use WAMR_BUILD_LINUX_PERF as the cmake compilation control - use WASM_ENABLE_LINUX_PERF as the compiler macro - use `wamrc --enable-linux-perf` to generate aot file which contains fp operations - use `iwasm --enable-linux-perf` to create perf map for `perf record`	2024-01-02 15:58:17 +08:00
Wenyong Huang	4a7a66e900	Enable wasm_runtime_terminate for single-threading (#2924) ... The host embedder may also want to terminate the wasm instance for single-threading mode, and it should work by setting exception to the wasm instance.	2023-12-26 16:05:44 +08:00
Wenyong Huang	5a75c31c38	Add VectorCombine pass for JIT and AOT (#2923) ... It improves performance for some cases. And add several vectorize related passes for JIT mode.	2023-12-26 11:27:20 +08:00
Wenyong Huang	1055c9884b	Refine wasm-c-api wasm_func_call (#2922) ... Refine params_to_argv, argv_to_results, wasm_func_param_arity, wasm_func_result_arity to fasten the wasm-c-api call wasm function process.	2023-12-26 11:05:31 +08:00
Daniel Mangum	9779f922b9	Fix boundary check typo in AOT compiler context (#2913) ... Fixes typo in docstrings for boundary check in the AOT compiler context. Signed-off-by: Daniel Mangum <georgedanielmangum@gmail.com>	2023-12-20 09:08:13 +08:00
Enrico Loparco	6dbfeb25dd	Expose API to set log level in embedder (#2907) ... Expose API `void wasm_runtime_set_log_level(log_level_t level)`.	2023-12-15 18:49:33 +08:00
YAMAMOTO Takashi	18529253d8	interpreter: Simplify memory.grow a bit (#2899)	2023-12-12 20:24:51 +08:00
Yage Hu	ef0cd22119	Fix memory size not updating after growing in interpreter (#2898) ... This commit fixes linear memory size not updating after growing. This causes `memory.fill` to throw an exception after `memory.grow`.	2023-12-12 08:36:59 +08:00
Enrico Loparco	4aee3cf14e	Avoid memory import failure when wasi-threads is enabled (#2893) ... According to the specification: ``` When instantiating a module which is expected to run with `wasi-threads`, the WASI host must first allocate shared memories to satisfy the module's imports. ``` Currently, if a test from the spec is executed while having the `multi-module` feature enabled, WAMR fails with `WASM module load failed: unknown import`. That happens because spec tests use memory like this: `(memory (export "memory") (import "foo" "bar") 1 1 shared)` and WAMR tries to find a registered module named `foo`. At the moment, there is no specific module name that can be used to identify that the memory is imported because using WASI threads: https://github.com/WebAssembly/wasi-threads/issues/33, so this PR only avoids treating the submodule dependency not being found as a failure.	2023-12-11 22:17:31 +08:00
Huang Qi	269b695f85	Refactor reloc symbols for riscv (#2894)	2023-12-11 14:44:41 +08:00
Yage Hu	bc2d8959dd	Handle ambiguous fstflags on fd_filestat_set_times (#2892) ... It's possible to set both `atim` and `atim_now` in the `fstflags` parameter. Same goes for `mtin` and `mtim_now`. However, it's ambiguous which time should be set in these two cases. This commit checks this and returns `EINVAL`.	2023-12-11 14:16:58 +08:00
Enrico Loparco	6cb2ea4935	fix command-reactor: Look for _initialize only if _start not found (#2891) ... A wasm module can be either a command or a reactor, so it can export either `_start` or `_initialize`. Currently, if a command module is run, `iwasm` still looks for `_initialize`, resulting in the warning: `can not find an export 0 named _initialize in the module`. Change to look for `_initialize` only if `_start` not found to resolve the issue.	2023-12-11 10:10:26 +08:00
Maks Litskevich	63696ba603	Fix typo in CI config and suppress STORE_U8 in TSAN (#2802) ... This typo prevented sanitizers to work in the CI.	2023-12-11 09:16:30 +08:00
Wenyong Huang	b008ab4fba	Fix possible dead lock in wasm_cluster_spawn_exec_env (#2882) ... Fix a deadlock issue like: wasm_runtime_spawn_exec_env wasm_cluster_spawn_exec_env (hold cluster->lock) wasm_runtime_instantiate_internal wasm_instantiate execute_post_instantiate_functions wasm_exec_env_set_module_inst (grab the lock again) Refer to #2879.	2023-12-08 17:28:57 +08:00
Yage Hu	0b332d8987	Portably handle fd_advise on directory fd (#2875) ... This commit adds a check to `fd_advise`. If the fd is a directory, return `ebadf`. This brings iwasm in line with Wasmtime's behavior. WASI folks have stated that fd_advise should not work on directories as this is a Linux-specific behavior: https://github.com/bytecodealliance/wasmtime/issues/6505#issuecomment-1574122949	2023-12-07 09:52:53 +08:00
Wenyong Huang	ac602bda32	Update version number to 1.3.0 and update release notes (#2821) ... And refine the code format for wasm_export.h.	2023-12-06 16:27:21 +08:00
Wenyong Huang	67a887e2d3	Fix compilation warnings on Windows (#2868)	2023-12-06 16:12:33 +08:00
Huang Qi	49cd2e011b	Fix float argument handling for riscv32 ilp32d (#2871)	2023-12-06 11:30:07 +08:00
Xu Jun	53c3fa27d4	Fix block with type issue in fast interp (#2866) ... Reported in https://github.com/bytecodealliance/wasm-micro-runtime/issues/2863.	2023-12-05 17:09:05 +08:00
Wenyong Huang	23c1343fb3	Fix wasm loader handle op_br_table and op_drop (#2864) ... - Fix op_br_table arity type check when the dest block is loop block - Fix op_drop issue when the stack is polymorphic and it is to drop an ANY type value in the stack	2023-12-05 16:59:13 +08:00
Huang Qi	e350e65b12	Don't add "+d" to riscv cpu features if already given (#2855)	2023-12-04 17:00:21 +08:00
Wenyong Huang	b0d5b8df1d	Fix issues of build/run with llvm-17 (#2853) ... - Fix compilation error of using PGOOptions - Fix LLVM JIT run error due to `llvm_orc_registerEHFrameSectionWrapper` symbol not found	2023-12-04 16:40:54 +08:00
Huang Qi	453a29a9d4	Enable spectest on riscv64 (#2843) ... Fix relocation issues on riscv and update test scripts and CI to enable test spec cases on riscv QEMU.	2023-12-04 14:22:47 +08:00
YAMAMOTO Takashi	73914caa9b	core/iwasm/interpreter/wasm_loader.c: remove an extra validation (#2845) ... * Empty names are spec-wise valid. * As we ignore unknown custom sections anyway, it's safe to accept empty names here. * Currently, the problem is not exposed on our CI because the wabt version used there is a bit old.	2023-12-01 18:29:15 +08:00
TianlongLiang	3d0342fbc8	Fix fast-jit accessing shared memory's fields issue (#2841) ... For shared memory, runtime should get the memories pointer from module_inst first, then get memory instance from memories array, and then get the fields of the memory instance.	2023-12-01 17:41:24 +08:00
liang.he	162a977006	Use wasm_config_t to pass private configuration to wasm_engine_new (#2837) ... Support new a wasm_config_t, set allocation and linux_perf_support options to it, and then pass it to wasm_engine_new_with_config to new an engine with private configuration.	2023-12-01 12:34:11 +08:00
liang.he	718f0671e7	Output warning and quit if import/export name contains '\00' (#2806) ... Leave it as a limitation when import/export name contains '\00' in wasm file. p.s. https://github.com/bytecodealliance/wasm-micro-runtime/issues/2789	2023-12-01 11:14:13 +08:00
Enrico Loparco	873558c40e	Get rid of compilation warnings and minor doc fix (#2839)	2023-11-30 08:49:58 +08:00
Enrico Loparco	0455071fc1	Access linear memory size atomically (#2834) ... Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2804	2023-11-29 20:27:17 +08:00
liang.he	8aa813f44a	Generate jitdump to support linux perf for LLVM JIT (#2788)	2023-11-27 15:42:00 +08:00
Marcin Kolny	5f7079f0f5	Return error when shutdown() fails (#2801) ... Fix issue reported in #2787.	2023-11-24 21:03:59 +08:00
Huang Qi	cb44e56b4e	Fix Zifencei extension issue in RISC-V (#2807) ... Refer to: https://github.com/bytecodealliance/wasm-micro-runtime/pull/2805	2023-11-23 10:23:33 +08:00
Jämes Ménétrey	f9e8b9535e	Attestation: Free JSON from the Wasm module heap (#2803) ... The JSON evidence is allocated on the module instance heap, but no API was given to dispose of this memory buffer. The sample mentions using the function free, which behaves differently depending on the execution context. This fix provides a new function called librats_dispose_evidence_json, enabling freeing the JSON evidence directly from the Wasm app.	2023-11-22 10:48:14 +08:00
Wenyong Huang	4d5eb346fc	Change is_shared_memory type from bool to uint8 (#2800) ... Change WASMMemoryInstance's field is_shared_memory's type from bool to uint8 whose size is fixed, so as to make WASMMemoryInstance's size and layout fixed and not break AOT ABI. See discussion in https://github.com/bytecodealliance/wasm-micro-runtime/pull/2682.	2023-11-22 10:38:08 +08:00
Huang Qi	0b29904f26	Fix configurable bounds checks typo (#2809)	2023-11-21 17:32:45 +08:00
Huang Qi	9ad42290d8	Fix formatting in wasm_dump_perf_profiling (#2799) ... Changes %d to %PRIu32.	2023-11-20 18:06:35 +08:00
Wenyong Huang	103cb89593	aot compiler: Fix handle next reachable if block (#2793) ... The popped reachable block may be if block whose else branch hasn't been translated, and should push the params for the else block if there are. And use LLVMDisposeMessage to free memory allocated in is_win_platform.	2023-11-20 17:14:10 +08:00
TianlongLiang	a57e70016a	Fix memory.init opcode issue in fast-interp (#2798) ... Fix fast interpreter didn't throw OOB exception correctly in some scenarios. Reported in #2797.	2023-11-20 16:25:43 +08:00
Huang Qi	aebe30426f	Fix formatting in aot_dump_perf_profiling (#2796) ... Changes %d to %PRIu32.	2023-11-20 12:11:02 +08:00
Huang Qi	e8c8f7fca6	Fix return type in wasm_loader_get_custom_section (#2794) ... Should return NULL instead of false.	2023-11-20 10:36:15 +08:00
YAMAMOTO Takashi	562a5dd1b6	Fix data/elem drop (#2747) ... Currently, `data.drop` instruction is implemented by directly modifying the underlying module. It breaks use cases where you have multiple instances sharing a single loaded module. `elem.drop` has the same problem too. This PR fixes the issue by keeping track of which data/elem segments have been dropped by using bitmaps for each module instances separately, and add a sample to demonstrate the issue and make the CI run it. Also add a missing check of dropped elements to the fast-jit `table.init`. Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2735 Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2772	2023-11-18 08:50:16 +08:00
TianlongLiang	08c0ec74c4	More precise help info of enabled targets for wamrc (#2783) ... Instead of printing all support targets of wamrc, print only the targets that are included in the LLVM library with which wamrc was compiled.	2023-11-17 19:05:00 +08:00
zoraaver	b39fd516d3	Use next generation crypto API on Windows (#2769) ... CryptGenRandom is deprecated by Microsoft and may be removed in future releases. They recommend to use the next generation API instead. See https://learn.microsoft.com/en-us/windows/win32/seccng/cng-portal for more details. Also, refactor the random functions to return error codes rather than aborting the program if they fail.	2023-11-17 18:40:29 +08:00
YAMAMOTO Takashi	2d0d4a0be9	Remove unused JitBitmap (#2775) ... Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2754	2023-11-16 18:48:06 +08:00
Huang Qi	b92906464e	Fix printing ref.extern addresses in wasm_application.c (#2774)	2023-11-16 15:10:58 +08:00
Wenyong Huang	dd0556a729	aot compiler: Disable musttail for thumb (#2771) ... Error is reported when executing `wamrc --target=thumb -o <aot_file> <wasm_file>`: ``` LLVM ERROR: failed to perform tail call elimination on a call site marked musttail Aborted (core dumped) ```	2023-11-16 11:05:23 +08:00
Wenyong Huang	9a32e0672c	Fix aot compiler issue reported by Coverity (#2770) ... Set `abi` to "gnu" for the bare-metal target when `abi` is NULL, or the below `bh_assert` and `bh_memcpy` may deference a NULL pointer. Error is reported when running wamrc compiled with `cmake .. -DCMAKE_BUILD_TYPE=Debug`: ``` core/iwasm/compilation/aot_llvm.c:2584:13: runtime error: null pointer passed as argument 1, which is declared to never be null ```	2023-11-16 10:54:39 +08:00
Huang Qi	24aa1cb408	Extend os_mmap to support map file from fd (#2763) ... Add an extra argument `os_file_handle file` for `os_mmap` to support mapping file from a file fd, and remove `os_get_invalid_handle` from `posix_file.c` and `win_file.c`, instead, add it in the `platform_internal.h` files to remove the dependency on libc-wasi. Signed-off-by: Huang Qi <huangqi3@xiaomi.com>	2023-11-16 08:28:54 +08:00
Wenyong Huang	0b8a904193	Fix fast-jit callnative translation (#2765) ... Lock i32 registers before and after preparing the function arguments to prevent they are overwritten.	2023-11-15 18:30:51 +08:00
zoraaver	8c27676718	Return uint32 from WASI functions (#2749) ... Returning uint16 from WASI functions is technically correct. However, the smallest integer type in WASM is int32 and since we don't guarantee that the upper 16 bits of the result are zero'ed, it can result in tricky bugs if the language SDK being used in the WASM app does not cast back immediately to uint16. To prevent this, we directly return uint32 instead, so that the result is well-defined as a 32-bit number.	2023-11-13 20:07:32 +08:00
Huang Qi	e4353b4e1f	Add eabihf ABI support and set vendor-sys of bare-metal targets (#2745) ... Set the vendor-sys of bare-metal targets to "-unknown-none-", and currently only add "thumbxxx" to the bare-metal target list. Signed-off-by: Huang Qi <huangqi3@xiaomi.com>	2023-11-13 18:01:15 +08:00
Haiyue Wang	625c95816d	Fix switch-case fallthrough compilation warning (#2753) ... The commit fa5e9d72b0 ("Abstract POSIX filesystem functions") introduces the build warning: ./core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src/posix.c: In function ‘fd_object_release’: ./core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src/posix.c:545:20: warning: this statement may fall through [-Wimplicit-fallthrough=] 545 | if (os_is_dir_stream_valid(&fo->directory.handle)) { | ^ ./core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src/posix.c:549:13: note: here 549 | default: | ^~~~~~~ Refer to the commit fb4afc7ca4 ("Apply clang-format for core/iwasm compilation and libraries"), add one line "// Fallthrough." to make compiler happy. Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>	2023-11-13 15:01:13 +08:00
Wenyong Huang	71340b79a6	Merge pull request #2740 from bytecodealliance/dev/wasi-libc-windows ... The implementation is already in a stage where it's possible to compile WAMR with wasi libc enabled and run wasi modules without errors.	2023-11-10 16:58:31 +08:00
YAMAMOTO Takashi	24c4d256b3	Grab cluster->lock when modifying exec_env->module_inst (#2685) ... Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2680 And when switching back to the original module_inst, propagate exception if any. cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/2512	2023-11-09 18:56:02 +08:00
Wenyong Huang	20f1a8c86c	Merge branch main into dev/wasi-libc-windows	2023-11-09 10:13:59 +08:00
Wenyong Huang	7f8292ffd1	Add more buffer boundary checks in wasm loader (#2734) ... And fix exception not printed in `iwasm --repl` mode and resize the memory data size to UINT32_MAX if the initial page number is 65536.	2023-11-09 08:42:05 +08:00
zoraaver	3c9cd40aa6	Provide default vprintf on UWP (#2725) ... UWP apps do not have a console attached so any output to stdout/stderr is lost. Therefore, provide a default BH_VPRINTF in that case for debug builds which redirects output to the debugger.	2023-11-07 20:37:43 +08:00
zoraaver	13875f43c6	Enable WASI tests on Windows CI (#2699) ... Most of the WASI filesystem tests require at least creating/deleting a file to test filesystem functionality so some additional filesystem APIs have been implemented on Windows so we can test what has been implemented so far. For those WASI functions which haven't been implemented, we skip the tests. These will be implemented in a future PR after which we can remove the relevant filters. Additionally, in order to run the WASI socket and thread tests, we need to install the wasi-sdk in CI and build the test source code prior to running the tests.	2023-11-06 19:24:06 +08:00
Wenyong Huang	e161205a27	Fix invalid use of jit_reg_is_const_val in fast-jit (#2718) ... `jit_reg_is_const_val` only checks whether the register is a const register and the const value is stored in the register. Should use `jit_reg_is_const` instead in the front end. Reported in #2710.	2023-11-03 14:25:26 +08:00
Wenyong Huang	caf805ece7	Fix AOT compiler simd shift opcodes (#2715)	2023-11-03 10:38:53 +08:00
Wenyong Huang	68a627ea2c	Fix several AOT compiler issues (#2697) ... - Fix potential invalid push param phis and add incoming phis to a un-existed basic block - Fix potential invalid shift count int rotl/rotr opcodes - Resize memory_data_size to UINT32_MAX if it is 4G when hw bound check is enabled - Fix negative linear memory offset is used for 64-bit target it is const and larger than INT32_MAX	2023-11-02 20:36:21 +08:00
Maks Litskevich	0b2313f6f8	Add tsan for fast interp and aot (#2679) ... To run it locally: ```bash export TSAN_OPTIONS=suppressions=<path_to_tsan_suppressions.txt> ./test_wamr.sh <your flags> -T tsan ``` An example for wasi-threads would look like: ```bash export TSAN_OPTIONS=suppressions=<path_to_tsan_suppressions.txt> ./test_wamr.sh -w -s wasi_certification -t fast-interp -T tsan ```	2023-11-01 18:30:25 +08:00
Wenyong Huang	52db362b89	Refine lock/unlock shared memory (#2682) ... Split memory instance's field `uint32 ref_count` into `bool is_shared_memory` and `uint16 ref_count`, and lock the memory only when `is_shared_memory` flag is true, no need to acquire a lock for non-shared memory when shared memory feature is enabled.	2023-10-31 11:46:03 +08:00
Wenyong Huang	4b1a6e5017	Fix repeatedly initialize shared memory data and protect the memory's fields (#2673) ... Avoid repeatedly initializing the shared memory data when creating the child thread in lib-pthread or lib-wasi-threads. Add shared memory lock when accessing some fields of the memory instance if the memory instance is shared. Init shared memory's memory_data_size/memory_data_end fields according to the current page count but not max page count. Add wasm_runtime_set_mem_bound_check_bytes, and refine the error message when shared memory flag is found but the feature isn't enabled.	2023-10-30 11:07:01 +08:00
Gavin Hayes	51a6b069d2	Fix use getrandom on cosmopolitan libc (#2674) ... Fixes the Cosmopolitan Libc platform attempting to use `/dev/urandom` on operating systems that do not have it. Signed-off-by: G4Vi <gavin@dylibso.com>	2023-10-27 14:07:16 +08:00
Alfred E. Neumayer	9b8fe049b3	core/iwasm: Support mapped file system access on non-libuv WASI (#2628) ... This patch enables mapping host directories to guest directories by parsing the `map_dir_list` argument in API `wasm_runtime_init_wasi` for libc-wasi. It follows the format `<guest-path>::<host-path>`. It also adds argument `--map-dir=<guest::host>` argument for `iwasm` common line tool, and allows to add multiple mappings: ```bash iwasm --map-dir=<guest-path1::host-path1> --map-dir=<guest-path2::host-path2> ... ```	2023-10-27 12:48:10 +08:00
Wenyong Huang	8038b9c524	Fix fast-jit f32/f64 truncate to i32/i64 (#2671) ... The f32/f64 value to be truncated may be a const, add checks for whether it is nan and whether it is out of the legal range. Fixes issue #2661.	2023-10-27 12:20:25 +08:00
zoraaver	e7a62d2099	Refactor clock functions to use WASI types (#2666) ... Refactoring the clock functions to use WASI types so we can simplify the code and remove some unnecessary boilerplate. See https://github.com/bytecodealliance/wasm-micro-runtime/pull/2637#discussion_r1362202879 for details.	2023-10-25 18:06:04 +08:00
Wenyong Huang	4f5ad4dc12	Apply no_sanitize_address for clang compiler in several places (#2663) ... Apply `no_sanitize_address` for clang compiler in several places in which it has been applied to gcc compiler. And refine the comment.	2023-10-25 08:05:26 +08:00
Wenyong Huang	d6bba13e86	Fix fast-interp "pre-compiled label offset out of range" issue (#2659) ... When labels-as-values is enabled in a target which doesn't support unaligned address access, 16-bit offset is used to store the relative offset between two opcode labels. But it is a little small and the loader may report "pre-compiled label offset out of range" error. Emitting 32-bit data instead to resolve the issue: emit label address in 32-bit target and emit 32-bit relative offset in 64-bit target. See also: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2635	2023-10-24 10:47:17 +08:00
Wenyong Huang	9d7931e1d2	Fix several typo/warning/unused-code issues (#2655) ... - Fix typo in wamr-test-suites script - Fix compilation warnings in libc-wasi posix.c - Remove unused code fast-jit jit_frontend.c - Remove duplicated exception print in `iwasm -f <function>` - Fix return value in void function wasm_runtime_set_wasi_ctx	2023-10-24 09:19:45 +08:00
fadumina1	a874bf0ff8	Implement wasi clock_time/clock_res get (#2637) ... Add os_clock_res_get and os_clock_time_get in platform_api_extension.h, and implement them in posix like platforms and windows platform.	2023-10-22 21:11:29 +08:00
zoraaver	fa5e9d72b0	Abstract POSIX filesystem functions (#2585) ... To allow non-POSIX platforms such as Windows to support WASI libc filesystem functionality, create a set of wrapper functions which provide a platform-agnostic interface to interact with the host filesystem. For now, the Windows implementation is stubbed but this will be implemented properly in a future PR. There are no functional changes in this change, just a reorganization of code to move any direct POSIX references out of posix.c in the libc implementation into posix_file.c under the shared POSIX sources. See https://github.com/bytecodealliance/wasm-micro-runtime/issues/2495 for a more detailed overview of the plan to port the WASI libc filesystem to Windows.	2023-10-19 19:19:39 +08:00
Marcin Kolny	72b34eaf30	Fix AOT shift operations for indirect constants (#2627) ... When doing more investigations related to this PR: https://github.com/bytecodealliance/wasm-micro-runtime/pull/2619 We found that in some scenarios the constant might not be directly available to the LLVM IR builder, e.g.: ``` (func $const_ret (result i32) i32.const -5 ) (func $foo (i32.shr_u (i32.const -1) (call $const_ret)) (i32.const 31) ) ``` In that case, the right parameter to `i32.shr_u` is not constant, therefore the `SHIFT_COUNT_MASK` isn't applied. However, when the optimization is enabled (`--opt-level` is 2 or 3), the optimization passes resolve the call into constant, and that constant is poisoned, causing the compiler to resolve the whole function to an exception.	2023-10-11 11:22:34 +08:00
liang.he	e73993709e	Use another default pipeline when opt-level is 0 (#2624) ... According to the description of `buildPerModuleDefaultPipeline()` and `buildLTOPreLinkDefaultPipeline()`, it is not allowed to call them with `O0` level. Use `buildO0DefaultPipeline` instead when the opt-level is 0.	2023-10-10 10:52:37 +08:00
Wenyong Huang	e222955f31	Merge branch main into dev/wasi-libc-windows	2023-10-09 09:24:00 +08:00
TianlongLiang	059fbfc252	Fix potential issue in aot compiler when translating block opcodes (#2622) ... The LLVM zext IR may be inserted after the terminator of a basic block when popping the arguments of a wasm block. Change to insert the zext IR before the terminator of the basic block to resolve the issue. Reported in #2620.	2023-10-08 09:17:54 +08:00
Wenyong Huang	7c22bde8dc	CI: Enable testing AOT multi-module feature (#2621) ... And refine some code pieces.	2023-10-08 08:36:49 +08:00
Marcin Kolny	b115b7baac	Fix compilation of shift opcodes on x86_64 and i386 architectures (#2619) ... This change fixes the case where the right parameter of shift operator is negative, specifically, when both parameters of shift opcode are constants.	2023-10-07 19:55:14 +08:00
Enrico Loparco	3668093053	Enable AOT usage on M1 mac (#2618)	2023-10-07 16:05:10 +08:00
Gavin Hayes	d8ee771e28	Add Cosmopolitan Libc Platform (#2598) ... This PR adds the Cosmopolitan Libc platform enabling compatibility with multiple x86_64 operating systems with the same binary. The platform is similar to the Linux platform, but for now only x86_64 with interpreter modes are supported. The only major change to the core is `posix.c/convert_errno()` was rewritten to use a switch statement. With Cosmopolitan errno values depend on the currently running operating system, and so they are non-constant and cannot be used in array designators. However, the `cosmocc` compiler allows non-constant case labels in switch statements, enabling the new version. And updated wamr-test-suites script to add `-j <platform>` option. The spec tests can be ran via `CC=cosmocc ./test_wamr.sh -j cosmopolitan -t classic-interp` or `CC=cosmocc ./test_wamr.sh -j cosmopolitan -t fast-interp`.	2023-10-04 21:55:37 +08:00
zoraaver	8987432f36	libc-wasi: Conditionally support SYNC flags (#2581) ... To make it clearer to users when synchronization behaviour is not supported, return ENOTSUP when O_RSYNC, O_DSYNC or O_SYNC are respectively not defined. Linux also doesn't support O_RSYNC despite the O_RSYNC flag being defined.	2023-10-04 21:02:25 +08:00
Maks Litskevich	28ebd57400	Refactor stress tests to make them runnable in reactor mode (#2614)	2023-10-04 08:10:10 +08:00
funera1	64baf54d88	Fix label index out-of-range references in op_br_table_cache (#2615) ... Fixed a bug in the processing of the br_table_cache opcode that caused out-of-range references when the label index was greater than the length of the label.	2023-10-03 10:33:00 +08:00
Zhen Kong	1a88104160	Remove module instance from hashmap in wasi_nn_destroy (#2613) ... When destroying wasi-nn context, module instance should be also removed from hashmap to avoid memory leak.	2023-10-03 08:33:11 +08:00
YAMAMOTO Takashi	e1ea15d94e	aot_resolve_stack_sizes: Disable the size check for now (#2608) ... cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/2555#issuecomment-1738530877 https://github.com/llvm/llvm-project/issues/67765	2023-09-29 15:30:52 +08:00
Enrico Loparco	00539620e9	Improve stack trace dump and fix coding guideline CI (#2599) ... Avoid the stack traces getting mixed up together when multi-threading is enabled by using exception_lock/unlock in dumping the call stacks. And remove duplicated call stack dump in wasm_application.c. Also update coding guideline CI to fix the clang-format-12 not found issue.	2023-09-29 10:52:54 +08:00
liang.he	3c17a36ccb	Patch implementations of vfbinop(min,max,pmin,pax) (#2584) ... According to the specification, - fNxM_pmin/max returns v1 or v2 based on flt(v1,v2) result - fNxM_min/max returns +/-NaN, +/-Inf, v1 or v2 based on more than flt(v1,v2) result Fixes issue #2561.	2023-09-28 09:32:01 +08:00
liang.he	cd0cec5beb	Check ValueKind before extracting a constant int value (#2595) ... Only when the value kind is LLVMConstantIntValueKind and the value is not undef and not poison can we extract the value of a constant int. Fixes #2557 and #2559.	2023-09-28 09:15:56 +08:00
dongsheng28849455	79b27c1934	Support muti-module for AOT mode (#2482) ... Support muti-module for AOT mode, currently only implement the multi-module's function import feature for AOT, the memory/table/ global import are not implemented yet. And update wamr-test-suites scripts, multi-module sample and some CIs accordingly.	2023-09-28 08:56:11 +08:00
Wenyong Huang	fff0e2ad1c	Fix nightly run sanitizer error in Fast JIT (#2601) ... Suppress a sanitizer integer overflow error in signed integer add operation in Fast JIT.	2023-09-27 15:41:48 +08:00
Wenyong Huang	6382162711	Fix loader push_pop_frame_ref_offset (#2590) ... `wasm_loader_push_pop_frame_offset` may pop n operands by using `loader_ctx->stack_cell_num` to check whether the operand can be popped or not. While `loader_ctx->stack_cell_num` is updated in the later `wasm_loader_push_pop_frame_ref`, the check may fail if the stack is in polymorphic state and lead to `ctx->frame_offset` underflow. Fix issue #2577 and #2586.	2023-09-26 10:17:54 +08:00
zoraaver	913a1414ad	Add support for closing/renumbering preopen fds (#2578) ... There doesn't appear to be a clear reason not to support this behavior. It seems it was disallowed previously as a precaution. See 67e2e57b02 for more context.	2023-09-26 09:31:32 +08:00
Alfred E. Neumayer	99b47fd334	Support AOT compiler with LLVM 17 (#2567) ... Adapt API usage to new interfaces where applicable, including LLVM function usage, obsoleted llvm::Optional type and removal of unavailable headers. Know issues: - AOT static PGO isn't enabled - LLVM JIT may run failed due to llvm_orc_registerEHFrameSectionWrapper isn't linked into iwasm	2023-09-25 19:00:46 +08:00
zoraaver	f474f3d668	Return __WASI_EINVAL from fd_prestat_dir_name (#2580) ... Return a WASI error code (rather than a host POSIX one). In addition, there is no need to return an error in the case that the provided buffer is too large.	2023-09-25 18:40:12 +08:00
TianlongLiang	71e07a7fa4	Fix potential unaligned store issue when extra return value is v128 (#2583) ... Unaligned store v128 value to the AOT function argument of the pointer for the extra return value may cause segmentation fault. Fix the issue reported in #2556.	2023-09-23 09:06:35 +08:00
zoraaver	06527f724e	Remove provision of unnecessary fd rights (#2579) ... The WASI docs allow for fewer rights to be applied to an fd than requested but not more. This behavior is also asserted in the rust WASI tests, so it's necessary for those to pass as well.	2023-09-22 09:11:25 +08:00
YAMAMOTO Takashi	444b159963	Implement async termination of blocking thread (#2516) ... Send a signal whose handler is no-op to a blocking thread to wake up the blocking syscall with either EINTR equivalent or partial success. Unlike the approach taken in the `dev/interrupt_block_insn` branch (that is, signal + longjmp similarly to `OS_ENABLE_HW_BOUND_CHECK`), this PR does not use longjmp because: * longjmp from signal handler doesn't work on nuttx refer to https://github.com/apache/nuttx/issues/10326 * the singal+longjmp approach may be too difficult for average programmers who might implement host functions to deal with See also https://github.com/bytecodealliance/wasm-micro-runtime/issues/1910	2023-09-20 18:11:52 +08:00
Enrico Loparco	83db970953	Add user to enlarge memory error callback (#2546)	2023-09-13 18:03:49 +08:00
YAMAMOTO Takashi	a6fda9b7ab	Add an API to terminate instance (#2538) ... Add API wasm_runtime_terminate to terminate a module instance by setting "terminated by user" exception to the module instance. And update the product-mini of posix platforms. Note: this doesn't work for some situations like blocking system calls.	2023-09-13 17:09:31 +08:00
YAMAMOTO Takashi	f128150d43	fd_object_release: Preserve errno (#2535) ... Preserve errno because this function is often used like the following. The caller wants to report the error from the main operation (`lseek` in this example), not from fd_object_release. ``` off_t ret = lseek(fd_number(fo), offset, nwhence); fd_object_release(fo); if (ret < 0) return convert_errno(errno); ```	2023-09-08 12:26:32 +08:00
YAMAMOTO Takashi	534a8cf9f4	Handle a return from wasi _start function correctly (#2529) ... This fixes a few test cases in wasi-threads testsuite like wasi_threads_return_main_block. And also move the special handling for "wasi proc exit" to a more appropriate place.	2023-09-08 11:49:04 +08:00
YAMAMOTO Takashi	6c846acc59	Implement module instance context APIs (#2436) ... Introduce module instance context APIs which can set one or more contexts created by the embedder for a wasm module instance: ```C wasm_runtime_create_context_key wasm_runtime_destroy_context_key wasm_runtime_set_context wasm_runtime_set_context_spread wasm_runtime_get_context ``` And make libc-wasi use it and set wasi context as the first context bound to the wasm module instance. Also add samples. Refer to https://github.com/bytecodealliance/wasm-micro-runtime/issues/2460.	2023-09-07 14:54:11 +08:00
Cengizhan Pasaoglu	af2f3c8759	Fix typo for IP address buffer (#2532)	2023-09-07 14:29:52 +08:00
YAMAMOTO Takashi	151dfae49c	Unifdef -U WASMTIME_SSP_STATIC_CURFDS (#2533) ... The macro WASMTIME_SSP_STATIC_CURFDS isn't used in the source code, remove the related macro control code.	2023-09-06 15:25:58 +08:00
Marcin Kolny	4798b69f36	Add ARM aeabi symbol for clearing memory content in a specific range (#2531)	2023-09-06 13:17:16 +08:00
Enrico Loparco	709127d631	Add callback to handle memory.grow failures (#2522) ... When embedding WAMR, this PR allows to register a callback that is invoked when memory.grow fails. In case of memory allocation failures, some languages allow to handle the error (e.g. by checking the return code of malloc/calloc in C), some others (e.g. Rust) just panic.	2023-09-05 16:41:52 +08:00
YAMAMOTO Takashi	48b71a05fb	libc-wasi: Remove unused code (#2528)	2023-09-04 19:14:56 +08:00
YAMAMOTO Takashi	9e3904337e	Revert "Return error when exception was raised after main thread finishes" (#2524) ... This reverts commit 71d43f3ca1.	2023-09-04 18:01:09 +08:00
YAMAMOTO Takashi	2e78230e06	set_exception_visitor: Remove the special case for wasi proc exit (#2525) ... While wasi proc exit is not a real trap, what the runtime does on it is mostly same as real traps. That is, kill the siblings threads and represent the exit/trap as the result of the "process" to the user api. There seems no reason to distinguish it from real traps here. Note that: - The target thread either doesn't care the specific exception type or ignore wasi proc exit by themselves. (clear_wasi_proc_exit_exception) - clear_wasi_proc_exit_exception only clears local exception.	2023-09-04 16:52:19 +08:00
Marcin Kolny	8c2dc1d011	Add unit tests for the tid allocator (#2519) ... Add simple infrastructure to add more unit tests in the future. At the moment tests are only executed on Linux, but can be extended to other platforms if needed. Use https://github.com/google/googletest/ as a framework.	2023-09-04 13:21:10 +08:00
YAMAMOTO Takashi	382d52fc05	Stop abusing shared memory lock to protect exception (#2509) ... Use a separate global lock instead. Fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2407	2023-08-31 20:39:08 +08:00
Marcin Kolny	53d7027de0	Implement strict validation of thread IDs according to the specification (#2521)	2023-08-31 20:23:54 +08:00
Maks Litskevich	411b903cee	Add mutex stress test (#2472) ... As a part of stress-testing we want to ensure that mutex implementation is working correctly and protecting shared resource to be allocated from other threads when mutex is locked. This test covers the most common situations that happen when some program uses mutexes like locks from various threads, locks from the same thread etc.	2023-08-30 19:01:44 +08:00
Jämes Ménétrey	ff151fb7ba	sgx-ra: Disable the building of samples (#2507)	2023-08-28 09:42:16 +08:00
Wenyong Huang	b7a9da1620	Merge branch main into dev/wasi-libc-windows	2023-08-23 17:05:19 +08:00
Wenyong Huang	858d1dd69c	Fix duplicate vector init in wasm_module_validate (#2498)	2023-08-23 12:35:46 +08:00
Huang Qi	051dfbbb9e	Fix a typo in is_win_platform (#2490)	2023-08-22 11:50:11 +08:00
liang.he	f0632edc37	Clone the input binary during wasm_module_validate (#2483)	2023-08-21 19:43:28 +08:00
Wenyong Huang	a2f76cf93c	Fix typo in aot_emit_aot_file.c (#2478)	2023-08-18 13:57:23 +08:00
Wenyong Huang	2cb701f7f3	Fix windows AOT hw bound check (#2475) ... When AOT out of bound linear memory access or stack overflow occurs, the call stack of AOT functions cannot be unwound currently, so from the exception handler, runtime cannot jump back into the place that calls the AOT function. We temporarily skip the current instruction and let AOT code continue to run and return to caller as soon as possible. And use the zydis library the decode the current instruction to get its size. And remove using RtlAddFunctionTable to register the AOT functions since it doesn't work currently.	2023-08-18 10:16:03 +08:00