391 Commits

Author	SHA1	Message	Date
Wenyong Huang	b038f2721b	Merge pull request #3823 from bytecodealliance/dev/shared_heap ... Implement the shared heap feature for interpreter, aot and llvm jit. Add below runtime APIs: ```C wasm_shared_heap_t wasm_runtime_create_shared_heap(SharedHeapInitArgs *init_args); bool wasm_runtime_attach_shared_heap(wasm_module_inst_t module_inst, wasm_shared_heap_t shared_heap); void wasm_runtime_detach_shared_heap(wasm_module_inst_t module_inst); uint64_t wasm_runtime_shared_heap_malloc(wasm_module_inst_t module_inst, uint64_t size, void **p_native_addr); void wasm_runtime_shared_heap_free(wasm_module_inst_t module_inst, uint64_t ptr); ``` And allow wasm app to call API shared_heap_malloc and shared_heap_free: ```C void *shared_heap_malloc(uint32_t size); void shared_heap_free(void *ptr); ```	2024-10-15 14:26:22 +08:00
Wenyong Huang	b16b6044ee	Enable libc-wasi for windows msvc build (#3852) ... The default iwasm building in Windows MSVC enables libc-uvwasi because libc-wasi isn't supported at the beginning. Since libc-wasi had been refactored and is supported in Windows msys2 building, and libc-wasi supports more functionalities(e.g. sockets) than libc-uvwasi, this PR fixes some issues to enable libc-wasi in windows MSVC buidlings.	2024-10-14 09:52:25 +08:00
TianlongLiang	36d438051e	Support table64 extension in classic-interp and AOT running modes (#3811) ... Add table64 extension(in Memory64 proposal) support in classic-interp and AOT running modes, currently still use uint32 to represent table's initial and maximum size to keep AOT ABI unchanged.	2024-10-11 21:14:56 +08:00
Wenyong Huang	deacb7a8d8	Fix exec_env_tls assertion in module instantiation (#3844) ... The execute_post_instantiate_functions may be triggered by wasm_cluster_spawn_exec_env, in which the exec_env_tls can be NULL and cause the assertion invalid. p.s. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3839.	2024-10-08 10:08:29 +08:00
Wenyong Huang	9ba36e284c	Implement shared heap for AOT (#3815)	2024-09-29 12:50:59 +08:00
Kvencc	438b81bd04	Fix missing symbols when using aot mode on riscv platforms (#3812) ... Add symbol __atomic_compare_exchange_4 and __atomic_store_4.	2024-09-28 21:55:09 +08:00
Wenyong Huang	e87f7a920d	Fix Windows compile error when uvwasi is enabled (#3810) ... No need to compile win_file.c when uvwasi is enabled.	2024-09-25 16:43:00 +08:00
Wenyong Huang	1fd422ae6e	Merge branch main into dev/shared_heap	2024-09-20 14:34:00 +08:00
Anders Bakken	21330990a8	Add no_resolve to LoadArgs and wasm_runtime_resolve_symbols (#3790) ... Add no_resolve to LoadArgs and wasm_runtime_resolve_symbols so one can delay resolving of symbols. This is useful for inspecting the module between loading and instantiating.	2024-09-20 08:54:09 +08:00
Liangyu Zhang	51a71092bf	Support dynamic aot debug (#3788) ... Enable dynamic aot debug feature which debugs the aot file and is able to set the break point and do single step. Refer to the README for the detailed steps. Signed-off-by: zhangliangyu3 <zhangliangyu3@xiaomi.com>	2024-09-18 11:02:10 +08:00
Benbuck Nason	d64a3ab6ec	Fix aot multi export memory support (#3791)	2024-09-14 10:53:01 +08:00
WenLY1	92852f3719	Implement a first version of shared heap feature (#3789) ... ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3546	2024-09-14 10:51:42 +08:00
Benbuck Nason	926f662231	Add memory instance support apis (#3786) ... Now that WAMR supports multiple memory instances, this PR adds some APIs to access them in a standard way. This involves moving some existing utility functions out from the `WASM_ENABLE_MULTI_MODULE` blocks they were nested in, but multi-memory and multi-module seem independent as far as I can tell so I assume that's okay. APIs added: ```C wasm_runtime_lookup_memory wasm_runtime_get_default_memory wasm_runtime_get_memory wasm_memory_get_cur_page_count wasm_memory_get_max_page_count wasm_memory_get_bytes_per_page wasm_memory_get_shared wasm_memory_get_base_address wasm_memory_enlarge ```	2024-09-14 10:31:13 +08:00
Marcin Kolny	9c2083a27f	Implement option for skipping function index in the callstack (#3785) ... Also add a script that converts instruction pointers to function indexes (or function names). https://github.com/bytecodealliance/wasm-micro-runtime/issues/3758	2024-09-11 16:08:37 +08:00
YAMAMOTO Takashi	f453d9d5ce	Appease GCC strict prototypes warning (#3775)	2024-09-10 09:42:23 +08:00
Marcin Kolny	cbc2078898	AOT call stack optimizations (#3773) ... - Implement TINY / STANDARD frame modes - tiny mode is only able to keep track on the IP and func idx, STANDARD mode provides more capabilities (parameters, stack pointer etc.). - Implement FRAME_PER_FUNCTION / FRAME_PER_CALL modes - frame per function adds code at the beginning and at the end of each function for allocating / deallocating stack frame, whereas in per-call mode the frame is allocated before each call. The exception is call to the imported function, where frame-per-function mode also allocates the stack before the `call` instruction (as it can't instrument the imported function). At the moment TINY + FRAME_PER_FUNCTION is automatically enabled in case GC and perf profiling are disabled and `values` call stack feature is not requested. In all the other cases STANDARD + FRAME_PER_CALL is used. STANDARD + FRAME_PER_FUNCTION and TINY + FRAME_PER_CALL are currently not implemented but possible, and might be enabled in the future. ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3758	2024-09-10 09:05:23 +08:00
Marcin Kolny	65521b188d	Remove unnecessary code duplication in aot runtime (#3767)	2024-09-05 11:10:18 +08:00
Anders Bakken	eab409a4df	aot loader: Call os_mmap with MMAP_MAP_32BIT only when target is x86-64 or riscv64 (#3755) ... Mac on aarch64 uses posix_memmap.c os_mmap which doesn't do anything with the flag MMAP_MAP_32BIT for that build so this condition ends up asserting unless the mapping ends up in the first 4 gigs worth of addressable space. Thsi PR changes to call os_mmap with MMAP_MAP_32BIT flag only when the target is x86-64 or riscv64, and the macro __APPLE__ isn't enabled. The behavior is similar to what the posix os_mmap does.	2024-08-29 15:25:17 +08:00
Anders Bakken	e8c2952bf9	Fix arm64 issues on mac (#3688) ... Make wamrc normalize "arm64" to "aarch64v8". Previously the only way to make the "arm64" target was to not specify a target on 64 bit arm-based mac builds. Now arm64 and aarch64v8 are treated as the same. Make aot_loader accept "aarch64v8" on arm-based apple (as well as accepting legacy "arm64" based aot targets). This also removes __APPLE__ and __MACH__ from the block that defaults size_level to 1 since it doesn't seem to be supported for aarch64: `LLVM ERROR: Only small, tiny and large code models are allowed on AArch64`	2024-08-23 09:49:06 +08:00
YAMAMOTO Takashi	b00904b092	Add a comment on AOT_SECTION_TYPE_SIGNATURE (#3746) ... cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3744	2024-08-22 12:35:25 +08:00
Wenyong Huang	67dce48201	Enable merged os_mmap for aot data sections and aot text (#3743) ... Enable merged os_mmap for aot data sections first, and try enabling merged os_mmap for them and aot text except on platform nuttx and esp-idf. This fixes the issue that aarch64 AOT module fails to load on android: https://github.com/bytecodealliance/wasm-micro-runtime/issues/2274 And also refine os_mmap related code.	2024-08-21 12:55:34 +08:00
Wenyong Huang	1329e1d3e1	Add support for multi-memory proposal in classic interpreter (#3742) ... Implement multi-memory for classic-interpreter. Support core spec (and bulk memory) opcodes now, and will support atomic opcodes, and add multi-memory export APIs in the future. PS: Multi-memory spec test patched a lot for linking test to adapt for multi-module implementation.	2024-08-21 12:22:23 +08:00
Huang Qi	6fdad9916f	riscv: Add missing relocation intrinsics for __fixdfsi/__ltdf2 (#3733)	2024-08-20 11:06:07 +08:00
Benbuck Nason	c05b93f992	aot runtime: Add missing arm/thumb relocations (#3660)	2024-07-25 11:06: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
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
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
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
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
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
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	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
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
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
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
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
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	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
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
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
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
YAMAMOTO Takashi	9d6d3466ff	Fix a few native stack address calculations (#3351)	2024-04-24 16:39:38 +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
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
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
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
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	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
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
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
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
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
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
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	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
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
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
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
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	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
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	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
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
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
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
tkernelcn	a2751903ff	freertos: Minor changes for freertos libc_wasi build adaption (#2973)	2024-01-04 09:49:24 +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
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
Huang Qi	269b695f85	Refactor reloc symbols for riscv (#2894)	2023-12-11 14:44:41 +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
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
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	9ad42290d8	Fix formatting in wasm_dump_perf_profiling (#2799) ... Changes %d to %PRIu32.	2023-11-20 18:06:35 +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
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
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
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	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
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
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
Wenyong Huang	7c22bde8dc	CI: Enable testing AOT multi-module feature (#2621) ... And refine some code pieces.	2023-10-08 08:36:49 +08:00