christoph/wamr
1
Fork 0
Code Releases Activity

fix: correct typos and improve comments across multiple files by codespell (#4116)

Browse Source 
Signed-off-by: Huang Qi <huangqi3@xiaomi.com>
This commit is contained in:
Huang Qi
2025-03-07 08:21:54 +08:00
committed by GitHub
parent 73998e4c85
commit 412631ac13
108 changed files with 215 additions and 215 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
product-mini/README.md
View File

@ -87,8 +87,8 @@ make
```
Note:
By default, the LLVM Orc JIT with Lazy compilation is enabled to speedup the lanuching process and reduce
the JIT compilation time by creating backend threads to compile the WASM functions parallely, and for the
By default, the LLVM Orc JIT with Lazy compilation is enabled to speedup the launching process and reduce
the JIT compilation time by creating backend threads to compile the WASM functions parallelly, and for the
main thread, the functions in the module will not be compiled until they are firstly called and haven't been
compiled by the compilation threads.
@ -114,7 +114,7 @@ mkdir build && cd build
cmake .. -DWAMR_BUILD_FAST_JTI=1 -DWAMR_BUILD_JIT=1
make
```
The Multi-tier JIT is a two level JIT tier-up engine, which launchs Fast JIT to run the wasm module as soon as possible and creates backend threads to compile the LLVM JIT functions at the same time, and when the LLVM JIT functions are compiled, the runtime will switch the extecution from the Fast JIT jitted code to LLVM JIT jitted code gradually, so as to gain the best performance.
The Multi-tier JIT is a two level JIT tier-up engine, which launches Fast JIT to run the wasm module as soon as possible and creates backend threads to compile the LLVM JIT functions at the same time, and when the LLVM JIT functions are compiled, the runtime will switch the extecution from the Fast JIT jitted code to LLVM JIT jitted code gradually, so as to gain the best performance.
## Linux SGX (Intel Software Guard Extension)
@ -335,7 +335,7 @@ $ cd build
$ cmake ..
$ make
$ # check output in distribution/wasm
$ # include/ includes all necesary head files
$ # include/ includes all necessary head files
$ # lib includes libiwasm.so
```
@ -350,7 +350,7 @@ $ cmake .. -DWAMR_BUILD_TARGET=AARCH64 -DANDROID_ABI=arm64-v8a # 64-bit ARM C
## NuttX
WAMR is intergrated with NuttX, just enable the WAMR in Kconfig option (Application Configuration/Interpreters).
WAMR is integrated with NuttX, just enable the WAMR in Kconfig option (Application Configuration/Interpreters).
## ESP-IDF

2
product-mini/platforms/common/libc_wasi.c
View File

@ -47,7 +47,7 @@ libc_wasi_print_help(void)
"--map-dir=<guest-path2::host-path2>\n");
printf(" --addr-pool=<addrs> Grant wasi access to the given network "
"addresses in\n");
printf(" CIDR notation to the program, seperated "
printf(" CIDR notation to the program, separated "
"with ',',\n");
printf(" for example:\n");
printf(" --addr-pool=1.2.3.4/15,2.3.4.5/16\n");

4
product-mini/platforms/linux-sgx/enclave-sample/App/App.cpp
View File

@ -153,7 +153,7 @@ enclave_init(sgx_enclave_id_t *p_eid)
return 0;
}
/* reopen the file with write capablity */
/* reopen the file with write capability */
fp = freopen(token_path, "wb", fp);
if (fp == NULL)
return 0;
@ -228,7 +228,7 @@ print_help()
printf(" to the program, for example:\n");
printf(" --dir=<dir1> --dir=<dir2>\n");
printf(" --addr-pool= Grant wasi access to the given network addresses in\n");
printf(" CIDR notation to the program, seperated with ',',\n");
printf(" CIDR notation to the program, separated with ',',\n");
printf(" for example:\n");
printf(" --addr-pool=1.2.3.4/15,2.3.4.5/16\n");
printf(" --max-threads=n Set maximum thread number per cluster, default is 4\n");

2
product-mini/platforms/linux-sgx/enclave-sample/App/pal_api.h
View File

@ -67,7 +67,7 @@ struct wamr_pal_create_process_args {
// Mandatory field. Must not be NULL.
const char *path;
// Argments array pass to new process.
// Arguments array pass to new process.
//
// The arguments to the command. By convention, the argv[0] should be the
// program name. And the last element of the array must be NULL to indicate

2
product-mini/platforms/nuttx/CMakeLists.txt
View File

@ -200,7 +200,7 @@ set(WAMR_ROOT_DIR ${CMAKE_CURRENT_LIST_DIR}/../../..)
# enable WAMR build system
include(${WAMR_ROOT_DIR}/build-scripts/runtime_lib.cmake)
# NuttX wamr lib complie required: `WAMR_SOURCES` `WAMR_CFLAGS` `WAMR_INCDIRS`
# NuttX wamr lib compile required: `WAMR_SOURCES` `WAMR_CFLAGS` `WAMR_INCDIRS`
# `WAMR_DEFINITIONS`
set(WAMR_SOURCES ${WAMR_RUNTIME_LIB_SOURCE})
set(WAMR_CFLAGS -Wno-shadow -Wno-unused-variable

2
product-mini/platforms/riot/Makefile
View File

@ -22,7 +22,7 @@ QUIET ?= 1
ARCHIVES += $(BINDIR)/libwamr.a
#Load the usual RIOT make infastructure
#Load the usual RIOT make infrastructure
include $(RIOTBASE)/Makefile.include

4
product-mini/platforms/rt-thread/iwasm.c
View File

@ -395,7 +395,7 @@ iwasm(int argc, char **argv)
else {
exception = app_instance_main(wasm_module_inst, argc - i_arg_begin,
&argv[i_arg_begin]);
rt_kprintf("finshed run app_instance_main\n");
rt_kprintf("finished run app_instance_main\n");
}
if (exception)
@ -448,4 +448,4 @@ fail1:
wasm_runtime_destroy();
return 0;
}
MSH_CMD_EXPORT(iwasm, Embeded VM of WebAssembly);
MSH_CMD_EXPORT(iwasm, Embedded VM of WebAssembly);

4
product-mini/platforms/zephyr/simple/README.md
View File

@ -47,9 +47,9 @@ to setup for local development.
## Building for a Specific Board
With an environment setup either locally or in a Docker container, you can build
for a Zephyr suppported board using
for a Zephyr supported board using
[`west`](https://docs.zephyrproject.org/latest/develop/west/index.html). There
are already [configuaration files](./boards) for a few boards in this sample.
are already [configuration files](./boards) for a few boards in this sample.
However, if you are using a new board, you will need to add your own file for
the board, or define configuration in the [`prj.conf](./prj.conf). After doing
so, use the following command with your board identifier to build the sample