You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**WAMR_BUILD_LIB_WASI_THREADS**=1/0, default to disable if not set
91
94
> Note: The dependent feature of lib wasi-threads such as the `shared memory` and `thread manager` will be enabled automatically.
92
95
96
+
> See [wasi-threads](./pthread_impls.md#wasi-threads-new) and [Introduction to WAMR WASI threads](https://bytecodealliance.github.io/wamr.dev/blog/introduction-to-wamr-wasi-threads) for more details.
97
+
93
98
#### **Enable lib wasi-nn**
94
99
-**WAMR_BUILD_WASI_NN**=1/0, default to disable if not set
100
+
> Note: See [WASI-NN](../core/iwasm/libraries/wasi-nn) for more details.
95
101
96
102
#### **Enable lib wasi-nn GPU mode**
97
103
-**WAMR_BUILD_WASI_NN_ENABLE_GPU**=1/0, default to disable if not set
> Note: if it is enabled, developer can use API `void wasm_runtime_dump_mem_consumption(wasm_exec_env_t exec_env)` to dump the memory consumption info.
138
144
Currently we only profile the memory consumption of module, module_instance and exec_env, the memory consumed by other components such as `wasi-ctx`, `multi-module` and `thread-manager` are not included.
139
145
146
+
> Also refer to [Memory usage estimation for a module](./memory_usage.md).
-**WAMR_BUILD_PERF_PROFILING**=1/0, default to disable if not set
142
150
> Note: if it is enabled, developer can use API `void wasm_runtime_dump_perf_profiling(wasm_module_inst_t module_inst)` to dump the performance consumption info. Currently we only profile the performance consumption of each WASM function.
143
151
144
152
> The function name searching sequence is the same with dump call stack feature.
145
153
154
+
> Also refer to [Tune the performance of running wasm/aot file](./perf_tune.md).
155
+
156
+
146
157
#### **Enable the global heap**
147
158
-**WAMR_BUILD_GLOBAL_HEAP_POOL**=1/0, default to disable if not set for all *iwasm* applications, except for the platforms Alios and Zephyr.
148
159
@@ -192,7 +203,7 @@ Currently we only profile the memory consumption of module, module_instance and
192
203
193
204
#### **Enable source debugging features**
194
205
- **WAMR_BUILD_DEBUG_INTERP**=1/0, default to 0 if not set
195
-
> Note: There are some other setup required by source debugging, please refer to [source_debugging.md](./source_debugging.md) for more details.
206
+
> Note: There are some other setup required by source debugging, please refer to [source_debugging.md](./source_debugging.md) and [WAMR source debugging basic](https://bytecodealliance.github.io/wamr.dev/blog/wamr-source-debugging-basic) for more details.
196
207
197
208
#### **Enable load wasm custom sections**
198
209
- **WAMR_BUILD_LOAD_CUSTOM_SECTION**=1/0, default to disable if not set
@@ -207,12 +218,34 @@ Currently we only profile the memory consumption of module, module_instance and
207
218
- **WAMR_BUILD_STACK_GUARD_SIZE**=n, default to N/A if not set.
208
219
> Note: By default, the stack guard size is 1K (1024) or 24K (if uvwasi enabled).
209
220
210
-
### **Disable the writing linear memory base address to x86 GS segment register
221
+
### **Disable the writing linear memory base address to x86 GS segment register**
211
222
- **WAMR_DISABLE_WRITE_GS_BASE**=1/0, default to enable if not set and supported by platform
212
223
> Note: by default only platform [linux x86-64](https://github.com/bytecodealliance/wasm-micro-runtime/blob/5fb5119239220b0803e7045ca49b0a29fe65e70e/core/shared/platform/linux/platform_internal.h#L67) will enable this feature, for 32-bit platforms it's automatically disabled even when the flag is set to 0. In linux x86-64, writing the linear memory base address to x86 GS segment register may be used to speedup the linear memory access for LLVM AOT/JIT, when `--enable-segue=[<flags>]` option is added for `wamrc` or `iwasm`.
213
224
225
+
> See [Enable segue optimization for wamrc when generating the aot file](./perf_tune.md#3-enable-segue-optimization-for-wamrc-when-generating-the-aot-file) for more details.
- **WAMR_BUILD_STATIC_PGO**=1/0, default to disable if not set
229
+
> Note: See [Use the AOT static PGO method](./perf_tune.md#5-use-the-aot-static-pgo-method) for more details.
230
+
231
+
### **Enable linux perf support**
232
+
- **WAMR_BUILD_LINUX_PERF**=1/0, enable linux perf support to generate the flamegraph to analyze the performance of a wasm application, default to disable if not set
233
+
> Note: See [Use linux-perf](./perf_tune.md#7-use-linux-perf) for more details.
234
+
235
+
### **Enable module instance context APIs**
236
+
- **WAMR_BUILD_MODULE_INST_CONTEXT**=1/0, enable module instance context APIs which can set one or more contexts created by the embedder for a wasm module instance, default to enable if not set:
237
+
```C
238
+
wasm_runtime_create_context_key
239
+
wasm_runtime_destroy_context_key
240
+
wasm_runtime_set_context
241
+
wasm_runtime_set_context_spread
242
+
wasm_runtime_get_context
243
+
```
244
+
> Note: See [wasm_export.h](../core/iwasm/include/wasm_export.h) for more details.
245
+
246
+
### **Enable quick AOT/JTI entries**
247
+
-**WAMR_BUILD_QUICK_AOT_ENTRY**=1/0, enable registering quick call entries to speedup the aot/jit func call process, default to enable if not set
248
+
> Note: See [Refine callings to AOT/JIT functions from host native](./perf_tune.md#83-refine-callings-to-aotjit-functions-from-host-native) for more details.
0 commit comments