-
Notifications
You must be signed in to change notification settings - Fork 749
Merge main into dev/fast_jit #1466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix wasm_type_equal check error in wasm_mini_loader.c: wasm_type_equal(type, j) -> wasm_type_equal(type, module->types[j]) And remove unused comments in aot_runtime.h
It's unused since the following commit: commit 260d36a
#1398) No one uses the `enable_debug` argument after the removal of wasm_runtime_create_exec_env_and_call_wasm.
Destroy Fast-JIT compiler after destroying the modules loaded by multi-module feature, since the Fast JIT's code cache allocator may be used by these modules. If the Fast JIT's code cache allocator was destroyed, then runtime will fail to destroy these modules. And fix the issue of destroying import module's memory instance.
They are no longer necessary because we no longer create debug instances automatically for exec env at this layer.
Add fast jit fixed virtual register import_func_ptrs_reg and func_type_indexes_reg for the preparation of further optimizations.
…1401) The entry and exit basic blocks might be destroyed before they are created. Found by instrument test. Add checks to fix the issue.
Leave the control from wasm_application_execute_main to host embedders, eg. product-mini.
Only destroy the block if it hasn't been pushed into the block stack, or it will be destroyed again when destroying the block stack.
process_port=1 means "use port 1"
Allow the embedder to manage port number for this purpose by itself.
Some configurations (eg. esp32/nuttx) have limited space for BSS, 0x20000 byte buffer is huge on embedded systems, change to allocate the buffer dynamically.
Change "==" to "=" when setting trunc_type[] array elements.
the corresponding nuttx PR: apache/nuttx-apps#1299
* add language bindings in README * minor update
To avoid mysterious behaviors caused by ignored errors.
Fix multi-module issue: don't call the sub module's function with "$sub_module_name$func_name" Fix the aot_call_function free argv1 issue Modify some API comments in wasm_export.h Fix the wamrc help info
hopefully this allows an extension package to run on multiple platforms. cf. https://code.visualstudio.com/api/extension-guides/debugger-extension#anatomy-of-the-package.json-of-a-debugger-extension
Add more checks for Fast JIT to fix the issues reported by instrument test: - add check for the jit_value before pushing it into the stack - add check at the end of form_and_translate_func - add checks after each jit pass
Report the memory leak info when building iwasm with `cmake .. -DWAMR_BUILD_GC_VERIFY=1`
Fix compilation warning: ``` wamr/product-mini/platforms/nuttx/../posix/main.c:622:5: warning: "WASM_ENABLE_SPEC_TEST" is not defined, evaluates to 0 [-Wundef] 622 | #if WASM_ENABLE_SPEC_TEST != 0 ``` Signed-off-by: Huang Qi <huangqi3@xiaomi.com>
…1441) Remove the workaround as it wasn't so good. (It can cause the lack of ctor calls) Mention that it's only about a command.
Enable building iwasm on Nuttx for target: * x86 * cortex-m0 * cortex-m4 * cortex-m7 * rv32imac * rv64imac * rv64gc
…ure (#1453) Use an empty string instead of stack garbage.
meshoptimizer repo had changed, change the patch accordingly.
Add library librats, update SGX build scripts, add sample and update document.
Set `WAMR_BUILD_LIB_PTHREAD_SEMAPHORE` for the sample, and update document.
Add the definition of `korp_sem` in platform_internal.h.
Add more checks for Fast JIT generating insn and jit_lock_reg_in_insn in compile_int_div_no_check and other places to avoid accessing NULL insn.
Should call `wasm_native_destroy` to destroy the registered native libs when registering native lib failed in `wasm_native_init`.
Remove handling opcode DROP_64/SELECT_64 in loader stage prepare_bytecode, as they are the modified opcodes of DROP/SELECT for optimization purpose, but not the opcodes defined by spec.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.