123 Commits

Author	SHA1	Message	Date
TianlongLiang	c4623e2cb5	Enable aot memory64 sw bounds checks by default (#4350) ... - enable aot memory64 sw bounds checks by default	2025-06-12 08:44:45 +08:00
liang.he	2a303861cc	Fix a linking error caused by commit #3580d1 (#4311) ... > **Fix a release-blocking issue** --- Like: ``` vmlib.lib(blocking_op.obj) : error LNK2019: unresolved external symbol __imp_wasm_runtime_begin_blocking_op referenced in function blocking_op_close [D:\a\wasm-micro-runtime\wasm-micro-runtime\wamr-compiler\build\wamrc.vcxproj] vmlib.lib(blocking_op.obj) : error LNK2019: unresolved external symbol __imp_wasm_runtime_end_blocking_op referenced in function blocking_op_close [D:\a\wasm-micro-runtime\wasm-micro-runtime\wamr-compiler\build\wamrc.vcxproj] ```	2025-06-02 16:30:51 +08:00
liang.he	3580d1a386	Enable runtime API exposure for MSVC builds (#4287)	2025-05-28 20:30:05 +08:00
liang.he	7f9e49213e	Enhance type checking for function types in loader and improve error handling (#4294) ... Especially when GC is enabled, a valid item of `module->types` needs additional checks before casting to WASMFuncType. Also, avoid overflowing if reftype_map_count is 0. Additionally, correctly set IN_OSS_FUZZ based on CFLAGS_ENV for sanitizer configuration. Update ASan and UBSan messages for clarity in non-oss-fuzz environments.	2025-05-28 20:29:09 +08:00
YAMAMOTO Takashi	908838a5b5	build-scripts/build_llvm.py: bump to llvm 18 (#4259) ... * build-scripts/build_llvm.py: bump to llvm 18 cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/4210 why not 20? because, as of writing this, 19 is the latest released version for the xtensa fork of llvm: https://github.com/espressif/llvm-project why not 19? because of a bug in the xtensa fork of llvm: https://github.com/espressif/llvm-project/issues/112 while we can use different versions for different targets, it's nicer to use the same version everywhere when possible. * spec-test-script/runtest.py: --size-level=0 for x86-64 with the recent version of LLVM, wamrc --size-level=1 often generates R_X86_64_32S relocations which fail on load with the infamous error: "relocation truncated to fit R_X86_64_32S failed" it seems that these relocations are often for jump tables. this commit workarounds it with --size-level=0. an alternative is to disable jump tables. (although it seems that jump tables are not the only source of these relocations.) cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3035 it might be better to do this in wamrc itself. however, currently target info is not available there in case of native compilation. related: https://github.com/bytecodealliance/wasm-micro-runtime/issues/3356 * wamr-compiler: size_level=0 for sgx mode cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3035	2025-05-09 17:14:02 +08:00
liang.he	5910e5cd21	Use --target to pass a triple in wamrc (#4199) ... Provide a triple string in the format of <arch>-<vendor>-<os>-<abi> via --target.	2025-05-06 06:56:06 +08:00
YAMAMOTO Takashi	84767f9121	wamrc: add --disable-llvm-jump-tables option (#4224) ... while ideally a user should not need to care this kind of optimization details, in reality i guess it's sometimes useful. both of clang and GCC expose a similar option. (-fno-jump-tables)	2025-04-28 16:43:53 +08:00
peter-tatrai	1f14f4ec0a	Fix build issues when compiling WAMRC as a cross-compiler (#4112) ... * Use CMAKE_INSTALL_BINDIR for wamrc installation * Fix wamrc build failure for 32bit non-x86 targets * Handle PIC flags by cmake in wamrc * Use dummy AOT reloc functions when building wamrc AOT reloc functions are used only when loading AOT WebAssembly modules on target, not during AOT compilation. Original code led to build issues when building wamrc as cross-compiler, using arm header on x86 build. * Add option to turn off SIMD support in wamrc	2025-03-20 14:24:30 +08:00
liang.he@intel.com	77e8a7d403	Refactor versioning documentation and adopt semantic versioning guidelines	2025-02-05 10:31:20 +00:00
liang.he@intel.com	b144e611a2	Add versioning information for libraries and executables across multiple platforms	2025-02-05 10:31:20 +00:00
liang.he	c6712b4033	add a validator for aot module (#3995) ... - Add AOT module validation to ensure memory constraints are met - Enable AOT validator in build configuration and update related source files	2025-02-05 15:21:49 +08:00
liang.he	53da420c41	Enable shrunk memory by default and add related configurations (#4008) ... - Enable shrunk memory by default and add related configurations - Improve error messages for memory access alignment checks - Add documentation for WAMR shrunk memory build option - Update NuttX workflow to disable shrunk memory build option	2025-01-13 07:09:04 +08:00
TianlongLiang	1af474099b	Add Windows wamrc and iwasm build in release CI (#3857) ... - For Windows, llvm libs need to cache more directories, so use a multi-line environment variable for paths - Remove conditionally build directories `win32build`, just use `build` for all platform - Add Windows wamrc and iwasm(disable lib pthread semaphore and fast jit for now) build in release CI	2024-10-17 10:01:56 +08:00
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
Wenyong Huang	9ba36e284c	Implement shared heap for AOT (#3815)	2024-09-29 12:50:59 +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
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	6f97822c18	Add wamrc parameter to configure stack frame features (#3763) ... Those parameters can be used to reduce the size of the AOT code. There's going to be more changes related to AOT code size reduction, this is just the initial step. p.s. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3758	2024-09-05 21:44:06 +08:00
TianlongLiang	d1141f6f30	aot compiler: Allow to control stack boundary check when boundary check is enabled (#3754) ... In the AOT compiler, allow the user to control stack boundary check when the boundary check is enabled (e.g. `wamrc --bounds-checks=1`). Now the code logic is: 1. When `--stack-bounds-checks` is not set, it will be the same value as `--bounds-checks`. 2. When `--stack-bounds-checks` is set, it will be the option value no matter what the status of `--bounds-checks` is.	2024-08-29 11:08:39 +08:00
Anders Bakken	e8c2952bf9	Fix arm64 issues on mac (#3688) ... Make wamrc normalize "arm64" to "aarch64v8". Previously the only way to make the "arm64" target was to not specify a target on 64 bit arm-based mac builds. Now arm64 and aarch64v8 are treated as the same. Make aot_loader accept "aarch64v8" on arm-based apple (as well as accepting legacy "arm64" based aot targets). This also removes __APPLE__ and __MACH__ from the block that defaults size_level to 1 since it doesn't seem to be supported for aarch64: `LLVM ERROR: Only small, tiny and large code models are allowed on AArch64`	2024-08-23 09:49:06 +08:00
Huang Qi	58ca02bc5f	Add support for RISCV32 ILP32F (#3708)	2024-08-15 15:17:42 +08:00
YAMAMOTO Takashi	6ddaecafb3	wamrc: Add some help text for --size-level (#3689)	2024-08-07 13:43:47 +08:00
YAMAMOTO Takashi	b21e3fd2fa	wamr-compiler: Avoid size-level tweak if target is specified (#3659) ... If target is specified, assume a cross-build. Partly fixes: https://github.com/bytecodealliance/wasm-micro-runtime/issues/3356	2024-07-25 10:39:48 +08:00
YAMAMOTO Takashi	b300797b71	wamrc: Add --mllvm= option (#3658) ... This allows users to specify llvm command line options, similarly to clang's -mllvm option. My motivations: * -debug and friends * -mtext-section-literals for xtensa	2024-07-24 20:25:45 +08:00
Byeongjee Kang	2cf48c8b9f	Fix typos in wamrc and wasm_export.h (#3609)	2024-07-10 12:05:58 +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
Wenyong Huang	a6e008bca7	document: Update description about segue opt, update README (#3338)	2024-04-22 14:34:52 +08:00
Wenyong Huang	63cd567b3f	Separate app-manager and app-framework from WAMR (#3129) ... As planned, the app-manager and app-framework are to be migrated to https://github.com/bytecodealliance/wamr-app-framework. ps. https://github.com/bytecodealliance/wasm-micro-runtime/issues/2329 https://github.com/bytecodealliance/wasm-micro-runtime/wiki/TSC-meeting-notes	2024-02-20 18:12:36 +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
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
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
Xavier Del Campo	ade97ac3e1	wamr-compiler: Fix non-x86{_64} host builds (#3037) ... The build system assumed sizeof (void *) == 8 as a host system running on a x86_64 architecture, x86 otherwise. However, this assumption is invalid for most other architectures out there, such as aarch64 or armv7l. This PR refers to the CMAKE_HOST_SYSTEM_PROCESSOR variable which, according to the documentation, typically refers to the output from "uname -m" for Unix-like systems.	2024-01-17 15:56:04 +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
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
liang.he	6c839042d6	Allow to control built-in libraries for wamrc from command line options (#2928) ... Allow to control built-in libraries for wamrc from command line options: ```bash cmake -DWAMR_BUILD_LIBC_WASI=1/0 cmake -DWAMR_BUILD_LIBC_BUILTIN=1/0 cmake -DWAMR_BUILD_LIB_PTHREAD=1/0 cmake -DWAMR_BUILD_LIB_WASI_THREADS=1/0 ``` And add some messages to show the status.	2023-12-28 22:20:55 +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
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
TianlongLiang	c820643b2b	wamrc: More friendly to print help info (#2451) ... Allow wamrc to print help info like below: ```bash wamrc --target=help wamrc --target-abi=help wamrc --target=<target> --cpu=help wamrc --target=<target> --cpu=help --cpu-features=+help ```	2023-08-16 11:28:45 +08:00
Florian Castellane	f34e7431fd	Fix typos in wamrc print_help() (#2442)	2023-08-09 14:31:02 +08:00
Huang Qi	aafea39b8c	Add "--enable-builtin-intrinsics=<flags>" option to wamrc (#2341) ... Refer to doc/xip.md for details.	2023-07-06 18:20:35 +08:00
Huang Qi	6a310cc88a	Add "--native-lib=<lib>" option to wamrc (#2342)	2023-07-06 12:25:28 +08:00
Huang Qi	44f4b4f062	Add "--enable-llvm-passes=<passes>" option to wamrc (#2335) ... Add "--enable-llvm-passes=<passes>" option to wamrc for customizing LLVM passes	2023-07-04 12:20:52 +08:00
Huang Qi	df98d9fb4a	Add "--xip" option for wamrc (#2336) ... Add shorthand "--xip" option for wamrc, which is equal to "--enalbe-indirect-mode --disable-llvm-intrinsics"	2023-07-04 12:03:40 +08:00
YAMAMOTO Takashi	ce6d1fd8fe	wamrc: Add an incompatibility note in the help message (#2276) ... An example of such optimizations: https://github.com/bytecodealliance/wasm-micro-runtime/pull/1752	2023-06-09 08:12:34 +08:00
YAMAMOTO Takashi	6e3c3fe9ec	Fix build error with LLVM 16 (#2259)	2023-06-06 13:45:18 +08:00
Wenyong Huang	8d88471c46	Implement AOT static PGO (#2243) ... LLVM PGO (Profile-Guided Optimization) allows the compiler to better optimize code for how it actually runs. This PR implements the AOT static PGO, and is tested on Linux x86-64 and x86-32. The basic steps are: 1. Use `wamrc --enable-llvm-pgo -o <aot_file_of_pgo> <wasm_file>` to generate an instrumented aot file. 2. Compile iwasm with `cmake -DWAMR_BUILD_STATIC_PGO=1` and run `iwasm --gen-prof-file=<raw_profile_file> <aot_file_of_pgo>` to generate the raw profile file. 3. Run `llvm-profdata merge -output=<profile_file> <raw_profile_file>` to merge the raw profile file into the profile file. 4. Run `wamrc --use-prof-file=<profile_file> -o <aot_file> <wasm_file>` to generate the optimized aot file. 5. Run the optimized aot_file: `iwasm <aot_file>`. The test scripts are also added for each benchmark, run `test_pgo.sh` under each benchmark's folder to test the AOT static pgo.	2023-06-05 09:17:39 +08:00
Wenyong Huang	76be848ec3	Implement the segue optimization for LLVM AOT/JIT (#2230) ... Segue is an optimization technology which uses x86 segment register to store the WebAssembly linear memory base address, so as to remove most of the cost of SFI (Software-based Fault Isolation) base addition and free up a general purpose register, by this way it may: - Improve the performance of JIT/AOT - Reduce the footprint of JIT/AOT, the JIT/AOT code generated is smaller - Reduce the compilation time of JIT/AOT This PR uses the x86-64 GS segment register to apply the optimization, currently it supports linux and linux-sgx platforms on x86-64 target. By default it is disabled, developer can use the option below to enable it for wamrc and iwasm(with LLVM JIT enabled): ```bash wamrc --enable-segue=[<flags>] -o output_file wasm_file iwasm --enable-segue=[<flags>] wasm_file [args...] ``` `flags` can be:     i32.load, i64.load, f32.load, f64.load, v128.load,     i32.store, i64.store, f32.store, f64.store, v128.store Use comma to separate them, e.g. `--enable-segue=i32.load,i64.store`, and `--enable-segue` means all flags are added. Acknowledgement: Many thanks to Intel Labs, UC San Diego and UT Austin teams for introducing this technology and the great support and guidance! Signed-off-by: Wenyong Huang <wenyong.huang@intel.com> Co-authored-by: Vahldiek-oberwagner, Anjo Lucas <anjo.lucas.vahldiek-oberwagner@intel.com>	2023-05-26 10:13:33 +08:00
TianlongLiang	7f5d9d4f5e	Update document for iwasm/wamrc dependent packages (#2183)	2023-05-08 16:30:56 +08:00
YAMAMOTO Takashi	2b896c80ef	wamrc: Add --stack-usage option (#2158)	2023-04-28 13:56:44 +08:00